Publishing an API involves making it available in a developer portal, ensuring that its endpoints are stable and reliable for other applications to use. As an API publisher, you are responsible for monitoring and managing daily API usage and handling various administrative tasks related to your APIs.

By following below steps, you can ensure a smooth and efficient process for publishing your API, making it accessible and reliable for developers and applications.

Note: Please ensure you are logged on to Anywhere Confluence for accessing below links.

Getting Started

This blog provides high level overview of steps and best practices for integrating your product/application with Datadog.

Here are steps for integration

What is Policy from ABAC Standpoint?

Policy is a set of rules that can be applied to specific API product to ensure only desired access is allowed for a specific consumer request.

You can set a policy with the attributes (properties) of the subject, object or action instead of themselves (the string) to control the access.

Why is Policy needed for ABAC?

What is user from ABAC Standpoint?

Users are part of organization and application. Admin can add in user and grant access to users to create/manage/view ABAC policies.

Why is application needed for ABAC?

User will create/view/Modify ABAC policies that are specific to application/organization.

Users with admin access can set policy rules at application level to control consumer access for specific attributes.

How to manage Users using ABAC UI?

What is application from ABAC Standpoint?

Application is nothing but API product that is available on Portal for consumer use.

• Application should have same name as API product name (name that appears on developer portal) from ABAC Standpoint.
• Organization owns API products (Applications) and ABAC Policies will control access to these API products to facilitate attribute level access.

Why is application needed for ABAC?

What is Organization from ABAC Standpoint?

Organization is a group that

• Owns API Product from ABAC Standpoint. It can be any publisher group that owns or wants to publish API product
• Owns API products (Applications) and ABAC Policies will control access to these API products to facilitate attribute level access.

Why is Organization needed for ABAC?

Tech

This blog describes the API versioning strategy and guidance of Anywhere APIs for publishers on how to implement it for their API products.

Semantic Versioning

API version numbers are in the format major.minor. Example, 3.12, where 3 is the major version and 12 is the minor version.

• A major version indicates a breaking (to the consumer) change from the previous major version, for example, removal of a field from the entity schema.

Anywhere Applications can use API-M ABAC solution to easily enforce attribute based control authorizations using this enterprise offering. This blog talk about Anywhere’s ABAC Implementation and how applications can take advantage of this solution and protect data from un-authorized users and actions.

What is ABAC?