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

Backstage Locations API

Endpoints for managing catalog locations (entity sources).

Backstage Locations API is one of 13 APIs that Backstage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://localhost:7007/api/auth.

6 operations 4 paths 4 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Server
https://localhost:7007/api/auth
Authentication
API Key, HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 2

Backstage Locations API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as backstage-auth (cookieAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth).

Paths & Operations 6

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

Locations 6

Endpoints for managing catalog locations (entity sources).

GET
/locations
Backstage List locations
getLocations → 200401
POST
/locations
Backstage Create a location
createLocation 1 param body → 201401409
GET
/locations/{id}
Backstage Get location by ID
getLocationById 1 param → 200404401
DELETE
/locations/{id}
Backstage Delete location
deleteLocation 1 param → 204404401
GET
/locations/by-entity/{kind}/{namespace}/{name}
Backstage Get location by entity
getLocationByEntity 3 params → 200404401
POST
/analyze-location
Backstage Analyze location
analyzeLocation body → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are EntityMetadata (10 properties), Entity (6 properties), Location (3 properties), EntityRelation (2 properties). Each schema is shown below with its type and property counts.

EntityMetadata
object
Metadata common to all entity kinds.
10 properties 1 required
Entity
object
A Backstage catalog entity.
6 properties 3 required
Location
object
3 properties
EntityRelation
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

backstage-locations-api-openapi.yml Raw ↑

Other APIs Backstage publishes across the network.

Backstage Events System
Backstage Actions API
Backstage Authentication API
Backstage Authorization API
Backstage Documentation API
Backstage Entities API
Backstage Metadata API
Backstage Search API
Backstage Sync API
Backstage Tasks API
Backstage Templates API
Backstage Token Verification API
Where this information came from

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