Queries all custom event sources.
Operation description
You can call this API operation to query custom event sources.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
eventbridge:ListUserDefinedEventSources | get | *EventSource acs:eventbridge:{#regionId}:{#accountId}:eventbus/{#EventBusName}/eventsource/* |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
NamePrefix | string | No | The name of the event source. | testName |
EventBusName | string | No | The name of the event bus. | testBus |
Limit | integer | No | The maximum number of entries to be returned in a call. You can use this parameter and NextToken to implement paging. Note: Up to 100 entries can be returned in a call. | 50 |
NextToken | string | No | If you configure Limit and excess return values exist, this parameter is returned. | 100 |
Response parameters
Sample responses: `HTTP/1.1 200 OK Server: AliyunEventBridge Connection: keep-alive Content-Type: application/json;charset=utf-8 Content-Length: 79 x-eventbridge-request-id: 608C6467-3195-42A3-97B5-C51FB976**** Date: Sat, 18 Apr 2020 05:30:41 GMT
{ "code":"200", "data":{ "RequestId":"608C6467-3195-42A3-97B5-C51FB976****", "Data":{ "eventSourceList":[ { "Status":"Activated", "Type":"UserDefined", "Ctime":1626360902642, "EventBusName": "demo-bus", "SourceRocketMQParameters":{ "InstanceId":"MQ_INST_164901546557****_BXmr****", "Tag":"", "RegionId":"cn-hangzhou", "Topic":"demo-topic", "GroupID":"GID_SOURCE", "Offset":"CONSUME_FROM_LAST_OFFSET" }, "ARN":"acs:eventbridge:cn-hangzhou:164901546557****:eventbus/my-event-bus/eventsource/myRocketMQ.source", "Name":"demo.source" } ] }, "Code":"Success", "Success":true }, "httpStatusCode":"200", "requestId":"608C6467-3195-42A3-97B5-C51FB976****", "successResponse":true }`
Examples
Sample success responses
JSON
format
{
"Message": "InvalidArgument",
"RequestId": "5169654A-7059-57E3-BFD9-33C7E012EA1B",
"Data": {
"NextToken": "100",
"Total": 18,
"EventSourceList": [
{
"Name": "rocketmq.source",
"Arn": "acs:eventbridge:cn-hangzhou:164901546557****:eventbus/my-event-bus/eventsource/myRocketMQ.source",
"Status": "Activated",
"Type": "UserDefined",
"Ctime": 1607071602000,
"ExternalSourceType": "RabbitMQ",
"EventBusName": "test-custom-bus",
"SourceMNSParameters": {
"RegionId": "cn-hangzhou",
"QueueName": "queue.openapi-sign-callback",
"IsBase64Decode": true
},
"SourceRocketMQParameters": {
"RegionId": "cn-shenzhen",
"InstanceId": "bastionhost-cn-7mz293s9d1p",
"Topic": "migration_instance",
"Tag": "dataact",
"Offset": "CONSUMEFROMLASTOFFSET",
"Timestamp": 1664591760,
"GroupId": "GID-test",
"InstanceType": "CLOUD_5",
"InstanceNetwork": "PublicNetwork",
"InstanceVpcId": "vpc-***",
"InstanceVSwitchIds": "vsw-bp1iu***",
"InstanceSecurityGroupId": "eb-167adad548***",
"AuthType": "ACL",
"InstanceEndpoint": "registry-vpc.cn-hangzhou.aliyuncs.com",
"InstanceUsername": "root",
"InstancePassword": "***"
},
"SourceRabbitMQParameters": {
"RegionId": "cn-hangzhou",
"InstanceId": "bastionhost-cn-0ju2x28fj07",
"VirtualHostName": "eb-connect",
"QueueName": "file-upload-queue"
},
"SourceSLSParameters": {
"Project": "VideoTestProject",
"LogStore": "cloudfirewall-logstore",
"ConsumePosition": "end",
"RoleName": "testRole"
},
"SourceHttpEventParameters": {
"Type": "HTTPS",
"Method": [
"GET"
],
"SecurityConfig": "none",
"Ip": [
"8.212.139.16/32"
],
"Referer": [
"aliyundoc.com\t"
],
"PublicWebHookUrl": [
"http://***.eventbridge.cn-hangzhou.aliyuncs.com/webhook/putEvents?token=***"
],
"VpcWebHookUrl": [
"http://***.eventbridge.cn-hangzhou-vpc.aliyuncs.com/webhook/putEvents?token=0f6705c9253540e1a53e06db011a25b52068562ca50d4818828fffd61c5af***"
]
},
"SourceKafkaParameters": {
"InstanceId": "i-2ze6kiwzkebf04s5h8ds",
"ConsumerGroup": "test-gid",
"Topic": "topic_api_1674441611897",
"OffsetReset": "earliest",
"RegionId": "cn-hangzhou",
"MaximumTasks": 2,
"Network": "Default",
"SecurityGroupId": "sg-f8zatts5g97x0j***",
"VpcId": "vpc-bp1kz3ohhzgrau2***",
"VSwitchIds": "vsw-bp1hcrxq3mkcik***e"
},
"SourceScheduledEventParameters": {
"Schedule": "0 1 * * * *",
"TimeZone": "GMT+0:00",
"UserData": "{\"a\": \"b\"}"
}
}
]
},
"Code": "Success",
"Success": true
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
403 | ServiceNotEnable | Service not enable |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-02-28 | The Error code has changed. The response structure of the API has changed | View Change Details |
2024-02-27 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-10-19 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-08-01 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-08-01 | The Error code has changed. The response structure of the API has changed | View Change Details |
2023-07-04 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2023-04-21 | The Error code has changed | View Change Details |