Version 4.0.0 of project44's API
Version 4.0.0 of project44's API
curl -i -X GET \ https://developers.project44.com/_mock/guides/shippers/visibility/ftl/api/api/v4/webhooks \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'
{ "webhookEndpoints": [ { … } ] }
webhookEndpoint
(Deprecated) The webhookAuthenticationMethod parameters. The subordinate fields for the 'authParams' field depend on the authType. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
(Deprecated) The webhookAuthenticationMethod type. BASIC, API_KEY and OAUTH2 are supported. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
A list of authentication methods. Each authentication method consists of 'type' and 'parameters' fields. Typically only one form of authentication is used, though it is possible to have two API keys or both an API key and OAuth2 authentication.
A unique identifier of the push configuration. Assigned by the push configuration API service and used for updates only.
The HTTP method associated with the webhook endpoint. If not provided, will default to POST.
A map of optional method parameters. If provided, these will appear as query parameters on the URL.
The format of the payload to send to the webhook. JSON is the only format supported.
curl -i -X PUT \ https://developers.project44.com/_mock/guides/shippers/visibility/ftl/api/api/v4/webhooks \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "authParams": {}, "authType": "API_KEY", "authenticationMethods": [ { "parameters": {}, "type": "API_KEY" } ], "configName": "string", "id": 0, "method": "GET", "methodHeaders": { "property1": "string", "property2": "string" }, "methodParams": {}, "payloadFormat": "JSON", "url": "string", "version": 0 }'
OK
(Deprecated) The webhookAuthenticationMethod parameters. The subordinate fields for the 'authParams' field depend on the authType. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
(Deprecated) The webhookAuthenticationMethod type. BASIC, API_KEY and OAUTH2 are supported. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
A list of authentication methods. Each authentication method consists of 'type' and 'parameters' fields. Typically only one form of authentication is used, though it is possible to have two API keys or both an API key and OAuth2 authentication.
A unique identifier of the push configuration. Assigned by the push configuration API service and used for updates only.
The HTTP method associated with the webhook endpoint. If not provided, will default to POST.
A map of optional method parameters. If provided, these will appear as query parameters on the URL.
The format of the payload to send to the webhook. JSON is the only format supported.
{ "authParams": {}, "authType": "API_KEY", "authenticationMethods": [ { … } ], "configName": "string", "id": 0, "method": "GET", "methodHeaders": { "property1": "string", "property2": "string" }, "methodParams": {}, "payloadFormat": "JSON", "url": "string", "version": 0 }
curl -i -X GET \ 'https://developers.project44.com/_mock/guides/shippers/visibility/ftl/api/api/v4/webhooks/{webhookId}' \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'
OK
(Deprecated) The webhookAuthenticationMethod parameters. The subordinate fields for the 'authParams' field depend on the authType. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
(Deprecated) The webhookAuthenticationMethod type. BASIC, API_KEY and OAUTH2 are supported. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
A list of authentication methods. Each authentication method consists of 'type' and 'parameters' fields. Typically only one form of authentication is used, though it is possible to have two API keys or both an API key and OAuth2 authentication.
A unique identifier of the push configuration. Assigned by the push configuration API service and used for updates only.
The HTTP method associated with the webhook endpoint. If not provided, will default to POST.
A map of optional method parameters. If provided, these will appear as query parameters on the URL.
The format of the payload to send to the webhook. JSON is the only format supported.
{ "authParams": {}, "authType": "API_KEY", "authenticationMethods": [ { … } ], "configName": "string", "id": 0, "method": "GET", "methodHeaders": { "property1": "string", "property2": "string" }, "methodParams": {}, "payloadFormat": "JSON", "url": "string", "version": 0 }
curl -i -X DELETE \ 'https://developers.project44.com/_mock/guides/shippers/visibility/ftl/api/api/v4/webhooks/{webhookId}' \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'
{ "httpStatusCode": 0, "httpMessage": "string", "errorMessage": "string", "errors": [ { … } ], "supportReferenceId": "string" }
curl -i -X GET \ 'https://developers.project44.com/_mock/guides/shippers/visibility/ftl/api/api/v4/webhooks/name/{webhookName}' \ -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'
OK
(Deprecated) The webhookAuthenticationMethod parameters. The subordinate fields for the 'authParams' field depend on the authType. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
(Deprecated) The webhookAuthenticationMethod type. BASIC, API_KEY and OAUTH2 are supported. This field is functional but is deprecated - authentication for new webhooks should be supplied in the 'authenticationMethods' field.
A list of authentication methods. Each authentication method consists of 'type' and 'parameters' fields. Typically only one form of authentication is used, though it is possible to have two API keys or both an API key and OAuth2 authentication.
A unique identifier of the push configuration. Assigned by the push configuration API service and used for updates only.
The HTTP method associated with the webhook endpoint. If not provided, will default to POST.
A map of optional method parameters. If provided, these will appear as query parameters on the URL.
The format of the payload to send to the webhook. JSON is the only format supported.
{ "authParams": {}, "authType": "API_KEY", "authenticationMethods": [ { … } ], "configName": "string", "id": 0, "method": "GET", "methodHeaders": { "property1": "string", "property2": "string" }, "methodParams": {}, "payloadFormat": "JSON", "url": "string", "version": 0 }