Reference · built on requestCommons signalHazards & public safety

IFRC GO

Emergencies, appeals, field reports, situation reports, and surge alerts from the IFRC GO platform's REST API.

Request accessPricing ↗

About

IFRC GO is the emergency operations platform of the International Federation of Red Cross and Red Crescent Societies. Its REST API at goadmin.ifrc.org exposes the records the GO site shows: emergencies (the event endpoint), operations (the appeal endpoint, typed DREF, Emergency Appeal, International Appeal, or Forecast Based Action), field reports, situation reports, flash updates, and surge alerts. Public data returns without a token. Records restricted to the Red Cross Red Crescent Movement need a GO account and a token from get_auth_token. Responses are paginated JSON or CSV in English, French, Spanish, or Arabic.

On Fibric, an operator watches new and updated emergencies in the countries where you ship, source, or run sites, and proposes an inbound delay notice, a shipping hold, or a site alert for your approval, with the GO event and its appeal code attached.

This is a reference listing. It documents what Fibric would read from IFRC GO and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Emergencies from /api/v2/event/: name, dtype, countries, disaster_start_date, ifrc_severity_level, glide, num_affected, and linked appeals
  • Operations from /api/v2/appeal/: code, atype, status, start_date, end_date, amount_requested, amount_funded, and num_beneficiaries
  • Surge alerts from /api/v2/surge_alert/: message, category, country, molnix_status, start, end, and the linked event
  • Situation reports from /api/v2/situation_report/: name, type, document_url, and the event they describe
  • Field reports from /api/v2/field-report/ and flash updates from /api/v2/flash-update/, both of which require a token
  • Disaster types from /api/v2/disaster_type/ and country and region records from /api/v2/country/ and /api/v2/region/
  • Event filters: disaster_start_date, created_at, and updated_at with __gte and __lte, plus dtype, appeal_type, countries__in, regions__in, and search

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Delay notice for inbound freight from an affected country

    Poll event with updated_at__gte and countries__in for your sourcing countries. When a new emergency lands with an appeal, the operator proposes a delay notice on open purchase orders and cites the GO event id.

    With Inbound Delay

  • Hold shipments into a declared emergency

    Match event countries and dtype to the destinations of your open orders. When a cyclone or flood emergency appears, the operator proposes a shipping hold and drafts the customer message.

    With Weather Hold

  • Alert a site team when a surge alert opens nearby

    Read surge_alert filtered by country__iso3. When an alert opens for a country where you run a site, the operator proposes a notice to the site lead with the alert message attached.

    With Severe Weather Notice

Requirements

  • The GO ids for the countries and regions you watch; regions__in runs 0 to 4 and countries__in takes the GO country id
  • Pagination with limit and offset; the wiki states the default page is 50 records and the maximum is 1000
  • A GO account and token only if you need field reports, flash updates, or other records limited to Movement members
  • Acceptance of the GO Terms and Conditions, which limit registered use to non-commercial purposes unless agreed with the data owner
Authentication
No credential for public records. A GO account with Red Cross Red Crescent permissions and a token from POST /get_auth_token, sent as Authorization: Token, for restricted records.

Limits

  • The OpenAPI schema lists filters but rarely describes them; the wiki data dictionary covers Event, Appeal, Surge Alert, and a few other endpoints
  • The appeal endpoint reads from AppealHistory and offers list only, with no single-record read
  • Events carry a source code (manual input, GDACS scraper, WHO scraper, field report, DREF) and a severity level; num_affected is a reported figure
  • The Terms and Conditions prohibit commercial use of registered data without a separate agreement and require the data source to be identified

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request IFRC GO ↗

Questions and answers

Do I need a token to read emergencies?
No. The wiki says data can be accessed without a token and only public data will be visible. The event, appeal, situation_report, and surge_alert endpoints list an anonymous option in the OpenAPI schema. Field reports and flash updates require tokenAuth, basicAuth, or cookieAuth.
How do I get a token?
POST your GO username and password as JSON to https://goadmin.ifrc.org/get_auth_token. The response includes token, expires, and your user id. Send it on later calls as Authorization: Token followed by the value. The wiki says a GO account with Red Cross Red Crescent permissions is required.
How is the data paged and formatted?
Every list endpoint takes limit and offset and returns count, next, previous, and results. The wiki states a default of 50 records and a maximum of 1000. Responses come as application/json or text/csv, and an Accept-Language header of en, fr, es, or ar selects the language.
Ask about IFRC GO

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by International Federation of Red Cross and Red Crescent Societies, IFRC GO (goadmin.ifrc.org). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy