> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/4.-developer-and-payment-engine/api-management.md).
# Team API
The Team API provides programmatic access to team-level resources, allowing developers to query and manage team-related data, including team accounts, wallets, billing information, and other team resources.Unlike the WaaS API, the Team API uses a Team API Key for authentication and authorization. Each API key is scoped to a single team and can only access resources within that team.The Team API enables seamless integration with internal business systems for automated operations, financial reconciliation, asset management, and other enterprise workflows.
## **Create API**
Go to Management > API Management and click Create.
On the Create API page, configure the following:
* API Name
* Permission
* IP Whitelist
Click Create.
Complete identity verification.
The API is created successfully.
**Note: Please copy and securely store your Secret Key. For security reasons, the complete Secret Key will not be displayed again.**
## **Edit API**
Go to Management > API Management and click Edit.
On the Edit API page, update the following settings as needed:
* API Name
* Permissions
* IP Whitelist
Click Save.
Complete identity verification.The API is updated successfully.
## **Enable / Disable API**
Go to Management > API Management and click Enable/Disable.
In the confirmation dialog, click Confirm.
Complete identity verification.The API is enabled or disabled successfully.
## **View API Key**
Go to Management > API Management and click More > View API Key.
Complete identity verification.
View and copy the API Key.
**Delete API**
Go to Management > API Management and click More > Delete.
In the confirmation dialog, click Confirm.
Complete identity verification.The API is deleted successfully.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.cregis.com/4.-developer-and-payment-engine/api-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
