Legacy Parameter Passing Method

Obtaining thirdTraceId

All API requests require a random string as thirdTraceId appended to the URL to identify each request. Therefore, each request must carry a different thirdTraceId. The random string should follow the RFC 4122 standard UUID Version 4 format.

• For non-technical users: Visit Online UUID Generator, click "Generate UUID" and copy the result.
• For technical users: Use the native UUID library of your programming language.

Example:

https://www.fxiaoke.com/cgi/crm/v2/data/get?thirdTraceId=5ea0422d-98e3-49e0-a3cb-9bd5517d1f30

Setting Request Headers

Before making each API request (except token requests), you must set the following request headers:

Required Parameters Explanation

authorization

Type: String

How to obtain: Fixed value "Bearer " followed by token

Note: There is a space after "Bearer"

Example: Bearer 1247D6096162AB2FDCEA46D6D7B74B33

x-fs-ea

Type: String

How to obtain: Check Client Credentials Mode, get "ea" from the response

Example: 12345

x-fs-userid

Type: String

How to obtain:

1. Click "CRM" application
2. Search for "Personnel"
3. Click the "System Name" of the target personnel
4. Find "Employee ID" in the account information, which is the x-fs-userid