Skip to content
AbloAblo Docs
Esc
navigateopen⌘Jpreview
On this page

Ablo API

Ablo collaboration infrastructure: commit, read, and claim. {model} is any model from your pushed schema — the routes are the same whichever it is. Authenticate every request with your API key as a Bearer token.

Versioning

Every route is mounted under /v1, and that segment is part of the address you call. A change that would break a caller — a field removed, a type narrowed, a status changed — arrives as a new segment beside this one, never as a change to this one. Additive changes do land here: a new field on a response, a new optional parameter, a new error code. Ignore what you do not recognize and you will not be broken by them.

Every response carries Ablo-Version, a date stamp for the contract the server is serving. Record the value your integration was built against and compare it if behavior surprises you.

Deprecation

A route being withdrawn says so on itself, for at least 180 days before it stops answering:

  • Deprecation — an sf-Date of when the deprecation took effect (RFC 9745). The route still answers normally while this is present.
  • Sunset — an HTTP-date of when it stops answering (RFC 8594).
  • Link with rel="deprecation" pointing at what to read, and rel="successor-version" at what to call instead when there is one.

The same operations are marked deprecated: true in this document. Treating either signal as a build failure is the intended use; nothing is removed without both.

Version 0.59.1
Base URLhttps://api.abloatai.com/apihttp://localhost:8787/api

models

claims

credentials

branches

schema

logs

commits

Was this page helpful?