Module management
Create a new module
The following steps need to be taken when creating a new module:
POST the new module to the modules endpoint. You will get an HTTP 202 (Accepted) response, with a link to the status endpoint.
Poll the status endpoint at regular intervals, but not more often than once every second.
Once the status endpoint returns a successful response, you will be redirected to the GET method of the modules endpoint. From this, you will get the NOBB module number.
Send the module for approval, using the module/sendforapproval endpoint, using the NOBB module number.
The approval process can be manual and may take a substantial amount of time. To check if the module approval process has finished, use the GET endpoint modules/{moduleno} and monitor the status.status property.
The approval has finished once the status.status is equal to "Godkjent" or "Underkjent".When status.status == "Godkjent" the module was approved, and when status.status == "Underkjent" the module was rejected.
Update an existing module
The following steps need to be taken when updating an existing module:
PATCH the changes to the module to the modules endpoint. NOBB Module number is the identifier for the module. You will get an HTTP 202 (Accepted) response, with a link to the status endpoint.
Poll the status endpoint at regular intervals, but not more often than once every second.
Once the status endpoint returns a successful response, you will be redirected to the GET method of the modules endpoint.
Send the module for approval, using the modules/sendforapproval endpoint, using the NOBB module number.
The approval process can be manual and may take a substantial amount of time. To check if the module approval process has finished, use the GET endpoint modules/{moduleno} and monitor the status.status property.
The approval has finished once the status.status is equal to "Godkjent" or "Underkjent".When status.status == "Godkjent" the module was approved, and when status.status == "Underkjent" the module was rejected.