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

Tribute Technology Serving Locations API

Funeral-home rooftops (serving locations) that obituaries attach to.

Tribute Technology Serving Locations API is one of 3 APIs that Tribute Technology publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Serving Locations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against 2 base URLs: https://api.tributecenteronline.com, https://api.demo.tributecenteronline.com.

4 operations 4 paths 4 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1
Base URL
https://api.tributecenteronline.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tribute Technology Serving Locations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — HTML bearer token obtained from POST /token/. Include as Authorization: Bearer {TOKEN}.

Paths & Operations 4

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

Serving Locations 4

Funeral-home rooftops (serving locations) that obituaries attach to.

POST
/api/external-location/post
Create or update a serving location (rooftop)
postExternalLocation body → 200400
GET
/api/locations/{servingLocationId}
Get a serving location
getLocation 1 param → 200
GET
/api/locations/
List all serving locations
listLocations → 200
GET
/api/locations/getlocationtypes
List location types
getLocationTypes → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ExternalLocation (14 properties), Location (13 properties), LocationType (2 properties), Message (1 property). Each schema is shown below with its type and property counts.

ExternalLocation
object
14 properties 3 required
Message
object
1 property
Location
object
13 properties
LocationType
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tributetech-serving-locations-api-openapi.yml Raw ↑

Other APIs Tribute Technology publishes across the network.

Tribute Technology Authentication API
Tribute Technology Obituaries API
Where this information came from

This is an independent, third-party profile of Tribute Technology Serving Locations 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.