Update certification types

PUT /references/certificationtypes/{TypeID}

Headers

  • The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC

    Format should match the following pattern: ^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \d{4} \d{2}:\d{2}:\d{2} (GMT|UTC)$.

  • The PSU's IP address if the PSU is currently logged in with the TPP.

  • An RFC4122 UID used as a correlation id.

  • Indicates the user-agent that the PSU is using.

Path parameters

  • TypeID string Required

    The UUID used to denote the certification type in question

    Maximum length is 40. Format should match the following pattern: ^[^<>]*$.

application/json

Body

  • Description of the certification type

    Format should match the following pattern: ^[^<>]*$.

  • ResourceType string Required

    Values are apiResource, apiDiscoveryEndpoint, authorisationServer, authorisationServerCertification, certificationManager, contact, organisation, organisationCertificate, organisationAdmin, organisationAuthorityClaim, organisationAuthorityClaimAuthorisations, organisationAuthorityDomainClaim, organisationAuthorityDomainClaimUser, organisationTermsAndConditions, softwareStatement, softwareStatementAuthorityRoleClaim, softwareStatementCertificate, softwareStatementCertification, referenceAuthorisationDomain, referenceAuthorisationDomainRole, referenceAuthorisationDomainRoleMetadata, referenceAuthority, referenceAuthorityAuthorisationDomain, referenceTermsAndConditions, or superUser.

  • Status string

    Current status of this resource

    Values are Active or Inactive. Default value is Active.

  • TypeName string Required

    Type name of the certification

    Format should match the following pattern: ^[^<>]*$.

Responses

  • 200 application/json

    Certification Type

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

    Hide response attributes Show response attributes object
    • CreatedAt string(date-time)
    • User who created the certification type

      Format should match the following pattern: ^[^<>]*$.

    • Description of the certification type

      Format should match the following pattern: ^[^<>]*$.

    • Values are apiResource, apiDiscoveryEndpoint, authorisationServer, authorisationServerCertification, certificationManager, contact, organisation, organisationCertificate, organisationAdmin, organisationAuthorityClaim, organisationAuthorityClaimAuthorisations, organisationAuthorityDomainClaim, organisationAuthorityDomainClaimUser, organisationTermsAndConditions, softwareStatement, softwareStatementAuthorityRoleClaim, softwareStatementCertificate, softwareStatementCertification, referenceAuthorisationDomain, referenceAuthorisationDomainRole, referenceAuthorisationDomainRoleMetadata, referenceAuthority, referenceAuthorityAuthorisationDomain, referenceTermsAndConditions, or superUser.

    • Status string

      Current status of this resource

      Values are Active or Inactive. Default value is Active.

    • TypeID string

      Type ID of the certification

      Maximum length is 40. Format should match the following pattern: ^[^<>]*$.

    • TypeName string

      Type name of the certification

      Format should match the following pattern: ^[^<>]*$.

  • 400 application/json

    Bad Request

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

    Hide response attribute Show response attribute object
    • errors array[string]

      Validation Error messages

  • Unauthorized

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • Forbidden

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • 404 application/json

    Not found

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

    Hide response attribute Show response attribute object
    • errors array[string]

      Validation Error messages

  • Conflict

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • Too many requests, maximum capacity reached. Requests are now throttled.

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • Internal Server Error

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • Bad Gateway

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

  • Upstream timeout, insufficient capacity to serve request. More capacity being brought online. Please try again.

    Hide headers attribute Show headers attribute
    • An RFC4122 UID used as a correlation id.

      Minimum length is 1, maximum length is 100. Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9\-]{0,99}$.

PUT /references/certificationtypes/{TypeID}
curl \
 -X PUT https://matls-api.sandbox.raidiam.io/references/certificationtypes/{TypeID} \
 -H "Authorization: Bearer $ACCESS_TOKEN" \
 -H "Content-Type: application/json" \
 -H "x-fapi-auth-date: string" \
 -H "x-fapi-customer-ip-address: string" \
 -H "x-fapi-interaction-id: string" \
 -H "x-customer-user-agent: string" \
 -d '{"Description":"string","ResourceType":"apiResource","Status":"Active","TypeName":"string"}'
Request examples
# Headers
x-fapi-auth-date: string
x-fapi-customer-ip-address: string
x-fapi-interaction-id: string
x-customer-user-agent: string

# Payload
{
  "Description": "string",
  "ResourceType": "apiResource",
  "Status": "Active",
  "TypeName": "string"
}
Response examples (200)
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d

# Payload
{
  "CreatedAt": "2025-05-04T09:42:00+00:00",
  "CreatedBy": "string",
  "Description": "string",
  "ResourceType": "apiResource",
  "Status": "Active",
  "TypeID": "string",
  "TypeName": "string"
}
Response examples (400)
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d

# Payload
{
  "errors": [
    "string"
  ]
}
Response examples (404)
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d

# Payload
{
  "errors": [
    "string"
  ]
}