Connect Federal Register to Amberscript

Both apps 18Federal Register 8Amberscript 10

• Trigger
  New document

  Polling trigger that fires when a new Federal Register document is published, using GET /documents.{format} sorted by publication_date descending as the dedup source for regulatory monitoring.

• Action
  Find documents

  Search all Federal Register documents published since 1994 by term, agency, document type, publication/effective date, and docket number. Endpoint: GET /documents.{format}

• Action
  Find public inspection documents

  Search public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}

• Action
  Get agency

  Fetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}

• Action
  Get document

  Fetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}

• Action
  Get issue

  Fetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}

• Action
  Get public inspection document

  Fetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}

• Action
  List agencies

  Fetch all agency details known to the Federal Register. Endpoint: GET /agencies

• Trigger
  Job Finished

  Triggers when a job has finished on our platform.

• Action
  Add glossary

  Create a new glossary of terms that can be referenced by glossaryId on job upload for improved transcription accuracy. POST https://api.amberscript.com/api/glossaries?apiKey={apiKey}.

• Action
  Create New Job

  This action creates a new job on the Amberscript platform.

• Action
  Delete glossary

  Delete an existing glossary. DELETE https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.

• Action
  Delete job

  Delete a transcription job. DELETE https://api.amberscript.com/api/jobs?jobId={jobId}&apiKey={apiKey}. Returns {"message":"Job deleted"}.

• Action
  Get job

  Retrieve the status/details of a transcription job. GET https://api.amberscript.com/api/jobs/status?jobId={jobId}&apiKey={apiKey}. Returns jobStatus with status OPEN/BUSY/ERROR/DONE, transcriptionType, jobType, language, nrAudioSeconds, etc.

• Action
  Get job transcript

  Download a finished job's transcript/subtitles in a chosen export format. GET https://api.amberscript.com/api/jobs/export-{format}?jobId={jobId}&apiKey={apiKey} where format is one of srt, vtt, txt, json (srt/vtt take optional maxCharsPerRow/maxNumberOfRows/maxScreenTimePerRowSeconds; txt takes optional includeTimestamps/includeSpeakers/highlightsOnly/maxCharsPerRow). SRT/VTT/JSON return the content directly (JSON export returns structured word-level data); TXT and STL(deprecated) return a downloadUrl JSON wrapper for some formats. Implementer should expose a format field and branch the endpoint/response handling accordingly.

• Action
  List glossaries

  List all glossaries defined on the account (used to supply glossaryId when uploading a job). GET https://api.amberscript.com/api/glossaries?apiKey={apiKey} per Amberscript docs Glossary section.

• Action
  List jobs

  List all transcription jobs for the account. GET https://api.amberscript.com/api/jobs?apiKey={apiKey}. Returns an array of jobStatus objects.

• Action
  Update glossary

  Update an existing glossary's terms. PUT/PATCH https://api.amberscript.com/api/glossaries/{glossaryId}?apiKey={apiKey}.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.