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

Create, read, update, and convert Leads.

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

Tagged areas include Leads. 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 6 operations across 3 paths, and defines 15 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.

6 operations 3 paths 15 schemas 1 DELETE2 GET1 PATCH2 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 Leads 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 6

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

Leads 6

Create, read, update, and convert Leads.

GET
/api/v1/leads
List Leads
listLeads 14 params → 200400401403
POST
/api/v1/leads
Create a Lead
createLead body → 201400401403
DELETE
/api/v1/leads/{lead_id}
Delete a Lead
deleteLead 1 param → 200400401403404
GET
/api/v1/leads/{lead_id}
Get a Lead
getLead 1 param → 200400401403404
PATCH
/api/v1/leads/{lead_id}
Update a Lead
updateLead 1 param body → 200400401403404
POST
/api/v1/leads/{lead_id}/convert
Convert a Lead
convertLead 1 param body → 200400401403404

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are V1LeadDetailPayload (23 properties), V1LeadSelectedFieldsPayload (23 properties), V1UpdateLeadRequest (16 properties), V1CreateLeadRequest (16 properties). Each schema is shown below with its type and property counts.

V1LeadDeletePayload
object
2 properties 2 required
V1LeadDetailResponsePayload
object
Single-Lead response envelope.
1 property 1 required
V1LeadDetailPayload
object
23 properties 23 required
V1PaginationPayload
object
Cursor pagination block for public list responses.
3 properties 3 required
V1UpdateLeadRequest
object
Request body for partially updating a Lead.
16 properties
V1LeadConversionResponsePayload
object
Lead conversion response envelope.
1 property 1 required
V1LeadConversionResultPayload
object
4 properties 4 required
V1ErrorResponse
object
Standard error envelope for all public v1 API errors.
1 property 1 required
V1LeadRelatedDealPayload
object
6 properties 6 required
V1LeadRelatedContactPayload
object
3 properties 3 required
V1LeadSelectedFieldsPayload
object
23 properties
V1ConvertLeadRequest
object
Request body for converting a Lead into an Account and Contact.
14 properties
V1LeadRelatedAccountPayload
object
2 properties 2 required
V1CreateLeadRequest
object
Request body for creating a Lead.
16 properties
V1LeadListPayload
object
Paginated list response for Leads.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fixture-leads-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 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 Leads 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.