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

Fixture Notes API

Create Notes linked to CRM entities.

Fixture Notes API is one of 11 APIs that Fixture publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://beta-api.fixture.app.

1 operations 1 paths 7 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://beta-api.fixture.app/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Fixture Notes API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API key or OAuth access token) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Send either a Fixture API key or a Fixture OAuth access token in the Authorization header as a bearer token.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Notes 1

Create Notes linked to CRM entities.

POST
/api/v1/notes
Create a Note
createNote body → 201400401403404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are V1ActivityDetailPayload (10 properties), V1CreateNoteRequest (4 properties), V1ActivityEntityPayload (3 properties), V1CreateNoteEntityLinkRequest (2 properties). Each schema is shown below with its type and property counts.

V1ActivityEntityPayload
object
3 properties 3 required
V1CreateNoteRequest
object
Request body for creating a Note attached to one primary CRM entity.
4 properties 3 required
V1ActivityDetailPayload
object
10 properties 10 required
V1ErrorResponse
object
Standard error envelope for all public v1 API errors.
1 property 1 required
V1NoteCreateResponsePayload
object
Created-Note response envelope.
1 property 1 required
V1CreateNoteEntityLinkRequest
object
2 properties 2 required
V1ActivityActorPayload
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fixture-notes-api-openapi.yml Raw ↑

Other APIs Fixture publishes across the network.

Fixture Accounts API
Fixture Activities API
Fixture Contacts API
Fixture Deals API
Fixture Fixture API API
Fixture Leads API
Fixture Pipelines API
Fixture Task Statuses API
Fixture Tasks API
Fixture Users API
Where this information came from

This is an independent, third-party profile of Fixture Notes 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.