Skip to content
FashionUnited Docs

Job Feed Inbound (JSON/XML)

FashionUnited’s feed service provides a full suite of real-time, highly available Jobboard transactions. This service opens the door to FashionUnited’s infrastructure and enables you to execute a wide variety of jobboard transactions empowering you to control your content at FashionUnited.

For an overview of all integration options, see Integrations Overview. To send your FashionUnited jobs to your own website instead, see Job Feed Outbound.

Setting Up the Connection

If you already see “FashionUnited” as an option in your applicant tracking system (ATS), it means a connection either already exists or can be activated. However, jobs will never go live automatically — we always need to set up or resume the connection on our side first.

Please note that some ATS providers may charge a setup fee (and in some cases an annual fee) to add FashionUnited as a publishing channel in their system. This is handled between you and your ATS provider.

What We Need From You

FashionUnited is the receiving party — we pull job data from your system, but we do not build the connection on your end. To get started, we need the following:

  • An endpoint: a URL (XML, RSS, API, or JSON) from which we can retrieve your vacancy data. This link should contain all your currently open positions, or alternatively, only the jobs you want to publish on FashionUnited.
  • If you already have an existing feed link (for example one you use for Indeed), we can often work with that as well.
  • If your system uses additional security (such as OAuth2), you’ll need to provide us with the required access token so we can retrieve the data.

How Synchronisation Works

  • The feed is synchronised hourly on weekdays, between 9 - 17h Amsterdam time.
  • New jobs will appear on FashionUnited after the next synchronisation.
  • Jobs that remain in the feed for more than 10 weeks are automatically republished to keep them visible.
  • To take a job offline, simply remove it from your ATS — it will disappear from FashionUnited after the next sync.
  • Any text changes (such as updated descriptions or titles) need to be made in your own system. The updates will be reflected on FashionUnited after the next synchronisation.

Content and Layout

The job content (text, title, location, etc.) comes from your feed. The visual layout and design are determined by the FashionUnited job template, ensuring a consistent look across all listings on our platform.

  • Logo: Your logo as SVG (or PNG) file
  • Images: 1 to 3 images (landscape format, 970 px wide, high resolution). All images need to have the same exact dimensions. Image(s) showcasing your brand. Think of showing part of your collection, the office, the team - a motive which gives potential candidates a good first impression.
  • Video: 1 video link (public video on YouTube or Vimeo)

In case of several brands: provide above per brand. We can set up a template per category (HQ / Retail); categories need to be clearly distinguishable via the feed.

Content of feed

Below is an overview of the information we need to receive through your job feed. If you have any questions about formatting or technical setup, don’t hesitate to reach out.

  1. Unique Job ID: Each job must have its own unique identifier (also called an external ID). This allows our system to clearly identify jobs.
  2. Job Title: Provide a clean job title without any extra details such as location or company name — just the title itself. This helps to multipost the jobs on aggregator sites (such as Google, Indeed, Jooble, JobRapido, CareerJet, Adzuna) - we do not control which jobs get picked up, however a “clean” job title field improves the chances.
  3. Job Category: FashionUnited uses the following categories: Design & Creative, Internships, Other, Product & Supply Chain, Retail Management & In-store, and Sales & Marketing. There are two ways to handle category assignment:
  • Automated mapping: If your categories differ from ours or are not included in the feed, we can automatically assign categories based on keywords in the job title or description. Jobs that don’t match any keyword will default to Retail Management & In-store.
  • Manual mapping: You can send us a complete list of your own categories, and we’ll create custom rules to match them with the FashionUnited categories.
  1. Teaser Text: A short summary or introduction for the job listing. If this isn’t provided, we’ll use the opening section of the job description instead.
  2. Job Description: The full vacancy text, including responsibilities, requirements, and any other relevant details.
  3. Location (City): The city where the job is based is required. Including the full street address is optional but recommended — it helps us display an accurate geolocation.
  4. Country: The country where the position is located.
  5. Company Name / Brand Name: The name of the hiring company and / or the brand name in case of several entities or brands. This way we can clearly identify and match logos and job layouts.
  6. Application Method: There are two options for handling applications:
  • Apply URL: Provide a unique link per job that directs candidates to the vacancy or application form on your own career site. All applications will then be managed through your own applicant tracking system (ATS). If you choose this option, let us know whether we should add a tracking parameter to the URL so you can monitor which applications come from FashionUnited.
  • Apply by Email: Provide an email address where applications should be sent. This option can replace an apply URL. Each time a candidate applies, an email notification will be sent to that address. You can also manage applicants through the FashionUnited Dashboard — contact our Customer Service team to request access.

Optional:

  • Which countries to exclude
  • Which positions to exclude

Send the feed URL and additional information and materials to jobs@fashionunited.com.

Example XML feed

Section titled “Example XML feed”
<?xml version="1.0" encoding="UTF-8"?>
<jobs>
  <job>
    <!-- unique id for the job in the external (your) system -->
    <externalId>00001</externalId>
    <!--
      title of the job
      can only contain the name of the position
      not the city, area or company
    -->
    <title>Design Assistant</title>
    <!--
      list of job categories
      supported categories are 'Design & Creative',
      'Internships', 'Other', 'Product & Supply Chain',
      'Retail Management & In-store', 'Sales & Marketing'
    -->
    <categories>
      <category><![CDATA[Design & Creative]]></category>
      <category>Internships</category>
    </categories>
    <!-- teaser text displayed in the job list, plaintext only, no HTML allowed -->
    <qualifications>Very teasing teaser</qualifications>
    <!--
      description of the job, HTML is allowed
      (when using templates, leave it empty)
      javascript is not allowed
    -->
    <description>
      <![CDATA[We are looking for a <em>motivated</em> employee, who...</description>]]>
    </description>
    <salary>
      <amount>2000</amount>
      <!-- salary currency in ISO 4217 -->
      <currency>EUR</currency>
    </salary>
    <!-- number of available positions -->
    <positions>2</positions>
    <!-- city of job location -->
    <city>Amsterdam</city>
    <!-- country of job location -->
    <country>Netherlands</country>,
    <!-- local address of company -->
    <address>Vijzelstraat 1234</address>
    <!-- list of platforms where the job is to be published -->
    <locales>
      <locale>nl-NL</locale>
    </locales>
    <!--
      true if the job receives applications via FashionUnited universal application form
      false otherwise (external Applicant Tracking System)
    -->
    <universalForm>true</universalForm>
    <!--
      show the job title between the company description and the job description
      should be false when using a template
    -->
    <showTitle>false</showTitle>,
    <company>
      <!-- the name of the company -->
      <name>Example Fashion</name>
      <!--
        description about company
        can be html as well
      -->
      <description>
        <![CDATA[Example Fashion is a <strong>great</strong> place to work...]]>
      </description>
      <!--
        the URL of the company logo, supports: SVG, PNG, JPEG
        SVG is recommended, since it's vector based and scalable
      -->
      <logoUrl>https://example.com/logos/logo.svg</logoUrl>
      <!--
        social media sharing image (og:image) URL, supports: PNG, JPEG
        PNG is recommended, since OpenGraph does not support SVG
        minimum size 200 x 200 pixels
        see: https://developers.facebook.com/docs/sharing/best-practices/
      -->
      <imageUrl>https://example.com/images/image.png</imageUrl>
      <!-- name of contact person from company -->
      <contact>John Smith</contact>
      <!-- company contact person's phone number -->
      <phone>012 345 6789</phone>
      <!--
        company contact person's email
        this email address is used to send applications
      -->
      <email>hr@example.com</email>
    </company>
  </job>
  <!-- ... -->
</jobs>