Stories and POVs
Create stories, attach POVs, update angle definitions, and work with story-level context.
- /stories
- /povs
- /stories/{id}/povs
Developer and Platform Teams
Integrate CiteLoop into your newsroom stack
Use API access to connect participants, stories, POV workflows, and downstream operations.
API overview
CiteLoop's API reflects the same workflow model as Engage: stories and POVs, participants, invitations, replies, assets, and render jobs.
Participants and contributor operations
Manage participant records, settings, consent, groups, and POV linkages.
- /participants
- /participants/groups
- /povs/{id}/participants
Invitations and outreach
Issue participant invitations, manage open invitation flows, and preview or send messaging workflows.
- /participants/{participant_id}/invitations
- /open-invitations
- /messages/preview
- /messages/send
Replies, assets, and rendering
Handle collected responses, process assets, and create asynchronous render jobs.
- /jobs/render
- /assets
- /objects
Access and scope
- API access is arranged through onboarding, not open self-serve signup.
- Your deployment may include a subset of the domains and paths above, depending on contract and use case.
- Path examples reflect the Engage workflow model. Scopes, credentials, and allowed endpoints are agreed during onboarding.
Contact info@the37lab.com for API credentials and onboarding.
Machine-readable overview: /data/api-overview.json
Questions about the CiteLoop API
Integration scope and access expectations.
Is the API publicly self-serve?
No. The API reflects the same workflow model as Engage. Access, credentials, and allowed endpoints are arranged through onboarding rather than open sandbox signup.
What domains does the API cover?
Stories and POVs, participants, invitations and open invitations, messages, replies and assets, and render jobs. The public overview lists representative paths; your contract may include a subset.
How do we authenticate?
Integrations use bearer-token authentication from the CiteLoop auth layer. Public participant flows use scoped access links instead of editor credentials.
Is there a machine-readable overview available?
Yes. See /data/api-overview.json for a JSON summary aligned with this page.
Can we rely on the OpenAPI file as a full contract?
The published OpenAPI spec documents a partial surface. Behavior and authorization for many routes are defined in the backend implementation and your onboarding agreement.
Connect CiteLoop to your existing stack
Use API onboarding to integrate participant sources, outreach, and creation workflows.