How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SingleFile organizations API

Organizations that own entities — CRUD plus contacts, documents, entities, orders and tasks

SingleFile organizations API is one of 7 APIs that SingleFile publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Organization. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 14 operations across 12 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.demo.singlefile.ai/external-api/v1.

14 operations 12 paths 21 schemas 8 GET1 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.demo.singlefile.ai/external-api/v1
Authentication
OAuth 2.0
License
BSD License
Terms of Service
Resource Areas
1

Authentication & Security 1

SingleFile organizations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow, exposing 2 scopes. By default, every request must be authenticated.

  • OAuth2ClientCredentials — OAuth 2.0 Client Credentials flow. Exchange clientid/clientsecret at the token endpoint for a 1-hour bearer token; send it as Authorization: Bearer .

Paths & Operations 14

Across 12 paths, the API surfaces 14 operations — 8 GET, 1 PATCH, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

organizations 14

Organizations that own entities — CRUD plus contacts, documents, entities, orders and tasks

POST
/organizations/{organization_id}/contacts/create
View to create contacts for an organization
organizations_contacts_create_create 1 param body → 201
GET
/organizations/{organization_id}/contacts
View to list all contacts associated with an organization
organizations_contacts_list 5 params → 200
PATCH
/organizations/{organization_id}/contacts/{contact_id}
View to retrieve and update a specific contact for an organization
organizations_contacts_partial_update 2 params body → 200
GET
/organizations/{organization_id}/contacts/{contact_id}
View to retrieve and update a specific contact for an organization
organizations_contacts_read 2 params → 200
PUT
/organizations/{organization_id}/contacts/{contact_id}
View to retrieve and update a specific contact for an organization
organizations_contacts_update 2 params body → 200
POST
/organizations/create
organizations_create_create body → 201
GET
/organizations/{organization_id}/documents
organizations_documents_list 9 params → 200
POST
/organizations/{organization_id}/documents/upload
organizations_documents_upload_create 1 param body → 201
GET
/organizations/{organization_id}/entities
organizations_entities_list 5 params → 200
POST
/organizations/{organization_id}/entity/create
organizations_entity_create_create 1 param body → 201
GET
/organizations/list
organizations_list_list 4 params → 200
GET
/organizations/{organization_id}/orders
organizations_orders_list 5 params → 200
GET
/organizations/{organization_id}
organizations_read 1 param → 200
GET
/organizations/{organization_id}/tasks
organizations_tasks_list 5 params → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Jurisdiction (35 properties), EntityCreate (21 properties), TaskInstance (21 properties), Governor (14 properties). Each schema is shown below with its type and property counts.

EntityList
object
6 properties 1 required
ExternalAddress
object
10 properties
OrderList
object
9 properties
OrganizationContactCreateRequest
object
3 properties
ContactDetail
object
12 properties 1 required
Governor
object
14 properties
TaskInstance
object
21 properties 1 required
GrossAsset
object
2 properties 2 required
ShareClass
object
5 properties 2 required
OrganizationList
object
7 properties
ContactUpdate
object
7 properties 1 required
DocumentList
object
10 properties 2 required
User
object
7 properties 3 required
ContactList
object
7 properties
EntityCreate
object
21 properties 7 required
OrganizationDetail
object
8 properties
OrganizationCreate
object
6 properties
DocumentUpload
object
8 properties 1 required
ContactCreate
objectnull
7 properties 3 required
Jurisdiction
object
35 properties
Address
objectnull
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

singlefile-organizations-api-openapi.yml Raw ↑

Other APIs SingleFile publishes across the network.

SingleFile documents API
SingleFile entities API
SingleFile jurisdictions API
SingleFile orders API
SingleFile schemas API
SingleFile tasks API
Where this information came from

This is an independent, third-party profile of SingleFile organizations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.