Simple api used for tracking holidays
Go to file
Borna Rajković 7a64afd767 Updated user pages 2023-12-31 13:35:29 +01:00
assets Updated user pages 2023-12-31 13:35:29 +01:00
db Database fix 2023-11-19 11:52:31 +01:00
holiday Updated user pages 2023-12-31 13:35:29 +01:00
migration Initial commit 2023-06-16 07:42:50 +00:00
templates Updated user pages 2023-12-31 13:35:29 +01:00
.gitignore Updated user pages 2023-12-31 13:35:29 +01:00
README.md Update 'README.md' 2023-08-25 06:07:35 +00:00
db.go Initial commit 2023-06-16 07:42:50 +00:00
docker-compose-deploy.yml Initial implementation 2023-06-20 16:10:46 +02:00
docker-compose.yml Initial implementation 2023-06-20 16:10:46 +02:00
dockerfile Updated design + added documentation page 2023-08-05 17:50:40 +02:00
go.mod Removed query editor 2023-07-11 21:38:13 +02:00
go.sum Removed query editor 2023-07-11 21:38:13 +02:00
handlers.go Updated user pages 2023-12-31 13:35:29 +01:00
main.go Updated user pages 2023-12-31 13:35:29 +01:00
makefile Fixed production migration + v0.2.2 -> v0.2.3 2023-08-05 22:10:15 +02:00
render.go Updated user pages 2023-12-31 13:35:29 +01:00

README.md

Holiday api

Simple api used for tracking holidays

Endpoints

Fetching is done via GET /api/v1/holidays endpoint

That endpoint accepts a list of required and optional parameters

Required parameters

country

  • determines for which country holidays are fetched, uses ISO 3166-1 Alpha-2 codes more info here
  • eg. country=US

Optional parameters

year

  • returns only holidays for given year
  • eg. year=2023
  • only used if no more important parameters are defined

date

  • returns only holidays for given date
  • date must be formatted in ISO 8601 format more info here
  • eg. date=2021-12-25
  • if defined year and rangeStart|rangeEnd parameters are ignored

rangeStart|rangeEnd

  • returns holidays in given range with both ends being inclusive
  • if either limit isn't defined it is assumed to be up to or all from given limit (if rangeStart isn't defined all holidays before rangeEnd are returned and vice-verse)
  • dates must be formatted in ISO 8601 format more info here
  • eg. rangeStart=2021-12-25&rangeEnd=2023-01-23, rangeStart=2023-01-20
  • if defined year parameter is ignored

stateHoliday

  • if set true only holidays that are tagged as state holidays are returned, similar for if set false, if not set all holidays are returned
  • eg. stateHoliday=true, stateHoliday=false

religiousHoliday

  • if set true only holidays that are tagged as religious holidays are returned, similar for if set false, if not set all holidays are returned
  • eg. religiousHoliday=true, religiousHoliday=false

Paging

pageSize

  • returns at most pageSize number of holidays
  • eg. pageSize=20
  • only applied if page is defined as well, by default set to 20

page

  • returns nth page of holidays, paging starts at 0
  • eg. page=0

Response

By default, responses are returned as a json array

{
  holidays: [{
    id: string;
    date: string(ISO 8601);
    name: string;
    description: string;
    isStateHoliday: boolean;
    isReligiousHoliday: boolean;
  },...]
}

eg.

{
  "holidays": [{
      "id": "74a2a769-abf2-45d4-bdc4-442bbcc89138",
      "date": "2023-12-25",
      "name": "Christmas",
      "description": "TBD",
      "isStateHoliday": true,
      "isReligiousHoliday": true
  }]
}

But can be returned as XML or CSV by setting appropriate Accept header (application/xml, text/xml or text/csv)

XML Response

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Holidays>
    <Holiday id="74a2a769-abf2-45d4-bdc4-442bbcc89138" date="2023-12-25" isReligious="true" isState="true">
        <name>Christmas</name>
        <description>TBD</description>
    </Holiday>
</Holidays>

CSV Response

id,date,name,description,is_state_holiday,is_religious_holiday
74a2a769-abf2-45d4-bdc4-442bbcc89138,2023-12-25,Christmas,TBD,true,true