Skip to content

Commit 261d144

Browse files
committed
update doc
1 parent 11360aa commit 261d144

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

ingest-app/docs/api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1157,7 +1157,7 @@ For NRT Notification subscriptions to be used there are three new fields that ar
11571157
<ul>
11581158
<li>Type: [required] Must be set to "granule" because NRT Notification subscriptions are only for granules.</li>
11591159
<li>CollectionConceptId: [required] Because type must be "granule", we must set "CollectionConceptId" as well, as indicated in Data Fields section</li>
1160-
<li>EndPoint: [required] describes where notifications get sent. At this time only AWS SQS ARN's are allowed. NRT Notification subscriptions that do not use an AWS SQS ARN will fail. If Batch Notification subscriptions are desired, do not use this field.</li>
1160+
<li>EndPoint: [required] describes where notifications get sent. At this time, only AWS SQS ARN's and HTTP/S URLs are allowed. HTTP/s URLs must be in the following full URL name format: https://www.websitename.com/123. If Batch Notification subscriptions are desired, do not use this field.</li>
11611161
<li>Mode: [required] describes whether the notification is for New (ingested for the first time into the CMR) granules, Updated granules, or Deleted granules. </li>
11621162
<ul>
11631163
<li>Valid values: "New", "Update", "Delete". Any combination of these values are valid and they are set using a json array. </li>
@@ -1181,7 +1181,7 @@ curl --request POST '%CMR-ENDPOINT%/ingest/subscriptions/my-native-id-of-my-sub
11811181
"SubscriberId": "My_sub_id",
11821182
"EmailAddress": "myemail@email.com",
11831183
"CollectionConceptId": "MyCollectionID",
1184-
"EndPoint": "MyAWSSQSARN",
1184+
"EndPoint": "MySQSARN",
11851185
"Mode": ["New","Update"],
11861186
"Method":"ingest",
11871187
"MetadataSpecification": {

0 commit comments

Comments
 (0)