This is a basic example to submit a prediction task for a specific useCase and modelId. Upon submission, the API responds with a unique predictionId and a status. The predictionId can be used later in the GET request to retrieve the results.
IMPORTANT: The available use cases are detailed in their own section in this specification.
The authentication and authorization access token.
application/json
The name of the use case for the model.
The unique identifier for the model.
Request information varies based on the use case in the request. See the specific use case for valid information for that use case.
The batch of key:value pairs used as inputs in the prediction. Up to 32 inputs per request are allowed.
32Provides fields and values that specify ranges for tokens. Fields used for specific use cases and models are specified. The default values are used if other values are not specified.
OK
This is the response to the POST prediction request submitted for a specific useCase and modelId.
The universal unique identifier (UUID) returned in the POST request. This UUID is required in the GET request to retrieve results.
The current status of the prediction. Allowed values are:
SUBMITTED - The POST request was successful and the response has returned the predictionId and status that is used by the GET request.
ERROR - An error was generated when the GET request was sent.
READY - The results associated with the predictionId are available and ready to be retrieved.
RETRIEVED - The results associated with the predicitonId are returned successfully when the GET request was sent.
"SUBMITTED"