Enable Cross-Enterprise Service Token Validation and Metadata Retrieval via Fabric Service Token API
Problem Statement
Customers who collaborate across multiple enterprises/accounts use Service Tokens to facilitate Equinix Fabric connectivity workflows. While Service Tokens can be shared and redeemed between different organizations, the current API appears to restrict retrieval and validation of Service Token details to the account context in which the token was created. When attempting to query a Service Token generated by another enterprise, the API GET /fabric/v4/serviceTokens/{serviceTokenId} returns an error rather than providing token status or metadata.
Customer Use Case
A receiving enterprise needs to validate the authenticity and status of a Service Token that was generated and shared by another enterprise before proceeding with provisioning workflows. Customers would like to programmatically verify:
- Whether the Service Token is valid
- Whether the token has been redeemed or remains available
- Allowed bandwidth
- Associated location/metro
- Relevant token attributes and parameters
- Expiration status and other metadata
This capability is particularly important for automation, partner integrations, and large-scale provisioning workflows where organizations exchange Service Tokens programmatically.
Requested Enhancement
Enhance the GET Fabric Service Token API to allow authorized cross-enterprise validation and retrieval of Service Token metadata when a valid Service Token ID is provided, subject to appropriate security and access controls.
Possible implementation options:
- Introduce a dedicated "Validate Service Token" API endpoint.
- Allow limited read-only access to token metadata for organizations that have received the token.
- Return non-sensitive token details while maintaining enterprise isolation.
- Provide token status and validation responses without exposing confidential account information.
Business Value
- Improves customer automation and self-service capabilities.
- Simplifies partner and multi-enterprise provisioning workflows.
- Reduces manual support cases related to Service Token validation.
- Improves operational efficiency for customers integrating Equinix Fabric APIs into their orchestration platforms.
- Enhances customer confidence when consuming shared Service Tokens from external enterprises.
Priority Justification
This represents a valid customer workflow where Enterprise A shares a Service Token with Enterprise B, and Enterprise B needs a reliable API mechanism to verify the token's authenticity, status, and key attributes before consuming it. The current limitation prevents full automation of this process and creates dependency on manual validation or support engagement.
Customer Impact: Medium to High for customers leveraging multi-enterprise Fabric automation and API-driven provisioning workflows.