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 Deals API

Create, read, update, and delete Deal records.

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

Tagged areas include Deals. 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 7 operations across 3 paths, and defines 20 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.

7 operations 3 paths 20 schemas 1 DELETE3 GET1 PATCH1 POST1 PUT

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 Deals 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 7

Across 3 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Deals 7

Create, read, update, and delete Deal records.

GET
/api/v1/deals
List Deals
listDeals 13 params → 200400401403
POST
/api/v1/deals
Create a Deal
createDeal body → 201400401403404
DELETE
/api/v1/deals/{deal_id}
Delete a Deal
deleteDeal 1 param → 200400401403404
GET
/api/v1/deals/{deal_id}
Get a Deal
getDeal 1 param → 200400401403404
PATCH
/api/v1/deals/{deal_id}
Update a Deal
updateDeal 1 param body → 200400401403404
GET
/api/v1/deals/{deal_id}/contacts
List Deal Contacts
listDealContacts 1 param → 200400401403404
PUT
/api/v1/deals/{deal_id}/contacts
Replace Deal Contacts
updateDealContacts 1 param body → 200400401403404

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are V1DealDetailPayload (15 properties), V1DealListItemPayload (13 properties), V1CreateDealRequest (9 properties), V1UpdateDealRequest (7 properties). Each schema is shown below with its type and property counts.

V1DealListPayload
object
Paginated list response for Deals.
2 properties 2 required
V1ErrorResponse
object
Standard error envelope for all public v1 API errors.
1 property 1 required
V1DealContactAssociationsResponsePayload
object
Deal-Contact association response envelope.
1 property 1 required
V1OwnerRelationshipSetUserPayload
object
User assignment entry for an owner relationship update.
1 property 1 required
V1OwnerUserPayload
object
User assigned through an owner relationship. Fetch user profile fields from /api/v1/users with users:read.
1 property 1 required
V1OwnerRelationshipPayload
object
Owner relationship state for an Account or Deal.
1 property 1 required
V1RelationshipsWritePayload
object
Relationship updates accepted on Account and Deal writes.
1 property
V1DealDetailPayload
object
15 properties 15 required
V1UpdateDealRequest
object
Request body for partially updating a Deal.
7 properties
V1DealContactPayload
object
4 properties 4 required
V1DealListItemPayload
object
13 properties 13 required
V1PaginationPayload
object
Cursor pagination block for public list responses.
3 properties 3 required
V1CreateDealRequest
object
Request body for creating a Deal.
9 properties 2 required
V1DealDetailResponsePayload
object
Single-Deal response envelope.
1 property 1 required
V1RelationshipsPayload
object
Relationships attached to an Account or Deal.
1 property 1 required
V1DealAssociationContactPayload
object
3 properties 3 required
UpdateDealContactsRequest
object
Request body for replacing the Contacts associated with a Deal.
2 properties 1 required
V1OwnerRelationshipWritePayload
object
Owner relationship update payload.
2 properties 1 required
V1DealContactAssociationPayload
object
3 properties 3 required
V1DealDeletePayload
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fixture-deals-api-openapi.yml Raw ↑

Other APIs Fixture publishes across the network.

Fixture Accounts API
Fixture Activities API
Fixture Contacts API
Fixture Fixture API API
Fixture Leads API
Fixture Notes 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 Deals 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.