Brandings

Brandings

Brandings allow hirers to promote their company brand on their job ads.
Each branding has a name and list of images:
  • The name is not visible to candidates but can help the hirer choose the appropriate branding for a job ad.
  • The images associated with a branding can be changed by the hirer which affects all live job ads.
A branding can either be active or inactive; it must be active to be used in job posting.
The SEEK API only supports querying of brandings at this time. Hirers can manage their brandings via the SEEK Employer website or by calling SEEK customer service.

Before you begin

Partners can use branding queries via partner and browser tokens.
  • SEEK recommends using a browser token to query brandings directly from a hirer’s browser. For the browser token to work, you will need to include the query:advertisement-brandings scope in your request.
  • You can also query brandings from your backend using a partner token.

Operations

Partners can use one of the following SEEK API queries for branding data:

advertisementBrandings

The advertisementBrandings query returns a paginated list of active brandings filtered by hirer.
QueryVariablesResult
query($after: String, $first: Int, $hirerId: String!) {
  advertisementBrandings(after: $after, first: $first, hirerId: $hirerId) {
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
      endCursor
    }
    edges {
      node {
        id {
          value
        }
        name
        images {
          typeCode
          url
        }
      }
      cursor
    }
  }
}
For subsequent queries you pass the previous page’s endCursor as the after argument. Once hasNextPage is false there are no more brandings to page through.

advertisementBranding

The advertisementBranding query returns the branding for a given branding ID if the branding exists and is active.
QueryVariablesResult
query($id: String!) {
  advertisementBranding(id: $id) {
    id {
      value
    }
    name
    images {
      typeCode
      url
    }
    hirer {
      id {
        value
      }
      name
    }
  }
}
Requesting the hirer.id is not necessary but can be useful for confirming that the branding is associated with the expected hirer.