GET /api/1/notice/submission/info/{submission_id}

This version 1 of this method is deprecated, but we still support it for now to provide backwards compatibility and we encourage the use of version 2 of this method instead. Version 2 also provides the ocid as part of response json, see GET api/2/notice/submission/info/{submission_id}.

Gets notice information for a published or non published notice as a NoticeInformation object.

Requires Authorization

The endpoint requires a Basic Auth in the http authorization header. For details, please see the Authentication section.

Request Information

URI Parameters

Name	Description	Type	Format	Max length	Example
submission_id	The submission id received when the notice was submitted	string	yyyymmdd-nnnnnn	15	20251029-123456
publication_number	The publication number of the notice	string	nnnnnn-yyyy or yyyynnnnnn	11	123456-2025 or 2025123456

Body Parameters

None.

Request Formats

GET

Sample:

/api/1/notice/submission/info/20251029-123456

Response Information

Resource Description

A NoticeInformation object containing details of the notice status.

Response Formats

In the case of successful response a NoticeInformation object is returned in JSON format.

application/json, text/json

Sample:

{
  "submission_id": "20251029-000050",
  "received_at": "2015-06-17T08:10:04Z",
  "status": "RECEIVED",
  "reason_code": null,
  "status_updated_at": "2015-06-17T08:10:04Z",
  "no_doc_ext": null,
  "form": null,
  "languages": [],
  "publication_info": null,
  "technical_validation_report": null,
  "validation_rules_report": null,
  "quality_control_report": null,
  "ref_submission_id": null,
  "ref_no_doc_ojs": null
}

In the case the wrong parameter name provided.

application/json, text/json

Sample:

{
  "timestamp": "2018-01-05T08:51:38Z",
  "status": 400,
  "error": "Bad Request",
  "message": "Request parameters unknown",
  "path": "/api/1/notice/submit",
  "exception": "Request parameter 'notices' is not recognised, no parameter expected"
}

In the case the Accept header is provided and set with a value different than ‘application/json’.

application/json, text/json

Sample:

{
  "timestamp": "2017-01-10T10:03:30Z",
  "status": 406,
  "error": "Not Acceptable",
  "message": "Not acceptable value for ‘Accept’ header. Only ‘application/json’ format is supported",
  "path": "/api/1/notice/submission/info/20251029-000004"
}

In the case the related notice could not be found.

application/json, text/json

Sample:

{
  "timestamp": "2017-01-10T10:03:30Z",
  "status": 404,
  "error": "Not Found",
  "message": "Notice not found",
  "path": "/api/1/notice/submission/info/20251029-000004"
}