> For the complete documentation index, see [llms.txt](https://docs.innopaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innopaas.com/api-reference/api-reference-en/overview/innopaas-api-getting-started-guide.md). # InnoPaaS API Getting Started Guide ## Interface Signature Verification Instructions ### Common Request Headers To ensure interface security, all interfaces need to include a security verification request header, Among them, Authorization and AppKey can be obtained only after creating an AppKey on the InnoPaaS platform Used for interface authentication verification; if verification fails, the interface cannot be called and an authentication failure will be returned.
No.FieldData TypeRequiredDescription
1Content-TypeStringYesThe value is "application/json;charset=utf-8", and the request content is JSON
2AppKeyStringYesApiKey, application access KEY
3AuthorizationStringYesAuthorization Token for application access
**Sample code for Headers** ```python headers = { 'Authorization': 'YUIYIUIAIIASUDIAOSIDUOIWUOQWUEOIUWOEUQWOEUOQWUOUWOUWQOWU', 'AppKey': 'XFbZY1rtTKo3UD4n1' } ``` ### Get AppKey **Create application**
**Copy AppKey:**Click the \[Copy] button in the application list to copy the AppKey
### Get Authorization 1\. Select an application and click the \[Token] button to generate the Authorization information needed for the production app to access the interface,**We will not store the customer's Token information. Each time a new one is generated, the previously generated Token will become invalid. If the Token of this App has already been used in your production environment, please use this feature with caution. The invalidation of the original Token may cause the API to become inaccessible normally.**
2\. Generate and copy the Token * Select the Token expiration time. The default is never expire, or you can specify an expiration date. * Click the \[Create Access Token] button to generate the Token * Click the \[Copy] button to copy the Token
## Configure WebHook callback address ### Configure WebHook events **When sending push templates, upstream reply messages, and other events, if the App cannot be identified or matched, the data will be pushed to the default application. If there is no default application at this time, it will not be pushed.** 1\. In the API Keys function menu list, click the callback event configuration button to start configuring
2\. Click the \[Add] button to add
3\. Select the product for which you need to configure the WebHook from the available product list
4\. Configure the callback address, select the events you want to receive, and click Next to proceed to the next step
5\. Select the callback request method. The default is POST. If the customer's business system needs to verify the source of the Webhook, you can configure the UserName and Authorization header information. When the WebHook notification is pushed, the UserName and Authorization will be added to the header information and the configured information will be pushed to the customer's system together**.**