DeckShift API
The API our own apps run on, opened to Enterprise customers by request.
The DeckShift phone apps and Chrome extension are both clients of one API. Enterprise customers can call it too, from a CRM workflow, an internal tool or a sales portal. We keep it private: there are no public docs and no self-serve keys, and access starts with a conversation.
What it covers
- List the seed decks your account holds.
- Start a shift from a seed deck and a prospect's website, with the same fields as a Quick Shift on the web.
- Follow a shift's progress, and answer its questions when it runs in question mode.
- Collect the finished deck's slides and a share link.
How access works
- 1Request access through the support form and tell us what you want to build.
- 2We hold a scoping call to agree the use case, the volumes and the endpoints you need.
- 3API access is written into your Enterprise agreement.
- 4You get credentials scoped to your account and the documentation for the endpoints you use.
Why it is not public
An API is a promise to keep things working. We would rather make that promise to a few customers we know than publish one we might have to break. Shifts started through the API draw on your account's tokens the same way a shift in the app does.
DeckShift API questions
Who can get API access?
Enterprise customers, by request. It is not part of the other plans.
Is there public documentation?
No. Customers with access get documentation for the endpoints they use, alongside their credentials.
Can we try it before signing?
Ask. The scoping call is where we work out whether a pilot makes sense for what you want to build.
Will the API ever be public?
Possibly, if enough customers ask for it. If it is, it will come with versioning and public documentation. We are not promising a date.
Request API access
Tell us what you want to build and roughly how many shifts a month. A founder reads every request and replies by email. Billing, seats and sign-in are covered in Help.