You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ingest-app/docs/api.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1157,7 +1157,7 @@ For NRT Notification subscriptions to be used there are three new fields that ar
1157
1157
<ul>
1158
1158
<li>Type: [required] Must be set to "granule" because NRT Notification subscriptions are only for granules.</li>
1159
1159
<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>
1161
1161
<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>
1162
1162
<ul>
1163
1163
<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
0 commit comments