- Function Overview
- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
APIs
-
Event Subscription Management
- Creating an Event Subscription
- Obtaining the Event Subscription List
- Updating an Event Subscription
- Obtaining Event Subscription Details
- Deleting an Event Subscription
- Updating an Event Subscription Source
- Creating an Event Subscription Target
- Updating an Event Subscription Target
- Obtaining Event Subscription Target Details
- Deleting an Event Subscription Target
- Event Channel Management
- Event Management
- Event Source Management
- Event Target Catalog Management
-
Event Schema Management
- Enabling or Disabling Event Subscriptions
- Creating a Custom Event Schema
- Obtaining the Event Schema List
- Updating a Custom Event Schema
- Obtaining Event Schema Details
- Deleting an Event Schema
- Creating a Custom Event Schema Version
- Obtaining the Event Schema Version List
- Obtaining Event Schema Version Details
- Deleting an Event Schema Version
- Starting Automatic Event Schema Discovery
- Connection Management
- Service Agency Management
- Quota Management
- API Version Management
- Trigger Management
- Endpoint Management
- OBS Bucket Management
- Metric Management
-
Event Subscription Management
- Permissions Policies and Supported Actions
- Appendix
- Description
- SDK Reference
-
FAQs
- How Is EG Billed?
- Why Did My Event Source Creation Fail?
- How Do I Configure a Security Group When Creating an Event Source?
- Why Did My Event Publishing Fail?
- Why Was the Target Not Triggered?
- Can I Push Custom Events to EG?
- Can I Send Custom Events in Batches? How Do I Encapsulate Them?
- How Do I Filter Events to Transmit to the Target?
- How Do I Transfer Custom Event Content to the Target?
Authentication
You can use either of the following authentication methods when calling APIs:
- Token authentication: Requests are authenticated using tokens.
- AK/SK authentication: Requests are encrypted using an AK/SK. AK/SK authentication is recommended because it is more secure than token authentication.
Token Authentication
A token is valid for 24 hours. If a token is required, the system caches the token to avoid frequent calling.
A token specifies temporary permissions in a computer system. During API authentication using a token, the token is added to request headers to get permissions for calling the API.
When calling an API to obtain a user token, you must set auth.scope in the request body to project.
{ "auth": { "identity": { "methods": [ "password" ], "password": { "user": { "name": "username", "password": "********", "domain": { "name": "domainname" } } } }, "scope": { "project": { "name": "xxxxxxxx" } } } }
After a token is obtained, the X-Auth-Token header field must be added to requests to specify the token when calling other APIs. For example, if the token is ABCDEFJ...., X-Auth-Token: ABCDEFJ.... can be added to a request as follows:
POST https://iam.eu-west-101.myhuaweicloud.com/v3/auth/projects Content-Type: application/json X-Auth-Token: ABCDEFJ....
AK/SK Authentication
AK/SK authentication supports API requests with a body not larger than 12 MB. For API requests with a larger body, token authentication is recommended.
AK/SK is used to sign requests and the signature is then added to the request headers for authentication.
- AK: a unique identifier used in conjunction with an SK to sign requests cryptographically.
- SK: used with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
The signing SDK is only used for signing requests and is different from the SDKs provided by services.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.