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

Fixie sip API

The sip API from Fixie — 3 operation(s) for sip.

Fixie sip API is one of 14 APIs that Fixie publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include SIP. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and an AsyncAPI specification.

This API exposes 7 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.0.3, at version 0.1.0.

Requests are made against a single base URL, https://api.ultravox.ai.

7 operations 3 paths 7 schemas 1 DELETE3 GET2 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.1.0
Base URL
https://api.ultravox.ai/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Fixie sip API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (apiKeyAuth).

  • apiKeyAuth — API key

Paths & Operations 7

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

sip 7
GET
/api/sip
sip_retrieve → 200
PATCH
/api/sip
sip_partial_update body → 200
GET
/api/sip/registrations
sip_registrations_list 2 params → 200
POST
/api/sip/registrations
sip_registrations_create body → 201
GET
/api/sip/registrations/{registration_id}
sip_registrations_retrieve 1 param → 200
PATCH
/api/sip/registrations/{registration_id}
sip_registrations_partial_update 1 param body → 200
DELETE
/api/sip/registrations/{registration_id}
sip_registrations_destroy 1 param → 204

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SipRegistration (8 properties), PatchedSipRegistration (8 properties), PatchedSipConfig (5 properties), SipConfig (5 properties). Each schema is shown below with its type and property counts.

PatchedSipRegistration
object
8 properties
SipRegistration
object
8 properties 6 required
SipConfig
object
5 properties 2 required
PaginatedSipRegistrationList
object
4 properties 1 required
AgentAllowance
object
2 properties 1 required
PatchedSipConfig
object
5 properties
FallbackHandler
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fixie-sip-api-openapi.yml Raw ↑

Other APIs Fixie publishes across the network.

Fixie accounts API
Fixie agents API
Fixie api_keys API
Fixie call_throttles API
Fixie calls API
Fixie corpora API
Fixie deleted_calls API
Fixie models API
Fixie schema API
Fixie telephony_configs API
Fixie tools API
Fixie voices API
Where this information came from

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