Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Match Data Center tables with Cloud API endpoints

For Data Center customers to understand the data and match Data Center tables with Cloud API endpoints by referring to these 2 documents:
https://help.tempo.io/kb/latest/tempo-data-center-database-tables
https://apidocs.tempo.io/

Before mapping, two important caveats so the result is accurate:

  1. apidocs.tempo.io is primarily the Cloud API (api.tempo.io/4/...). Tempo DC has its own REST API (documented at apidocs.tempo.io/dc/... and at tempo.io/server-api-documentation), but the resource groupings are nearly identical. Below I use the Cloud-style paths from apidocs.tempo.io; on DC the same paths are reached via /rest/tempo-core/, /rest/tempo-timesheets/4/, /rest/tempo-teams/2/, /rest/tempo-accounts/1/, and /rest/tempo-planning/1/.

  2. Not every DC table has a public endpoint. Several tables back UI features only (Folios/Portfolios, saved reports, favorites, permission groups, expenses, etc.). I've flagged those explicitly so you don't go hunting for an endpoint that doesn't exist.

Tempo Core (AO_013613_*)

DC table

Stores

API endpoint group (http://apidocs.tempo.io )

AO_013613_HD_SCHEME

Holiday schemes

/holiday-schemes (Holiday Schemes)

AO_013613_HD_SCHEME_DAY

Holidays in a scheme

/holiday-schemes/{id}/holidays

AO_013613_HD_SCHEME_MEMBER

Members of a holiday scheme

/holiday-schemes/{id}/members, /holiday-schemes/users/{accountId}

AO_013613_WL_SCHEME

Workload schemes

/workload-schemes (Workload Schemes)

AO_013613_WL_SCHEME_DAY

Working hours per day in a scheme

/workload-schemes (days are nested in the scheme payload)

AO_013613_WL_SCHEME_MEMBER

Members of a workload scheme

/workload-schemes/{id}/members, /workload-schemes/users/{accountId}

AO_013613_WORK_ATTRIBUTE

Work attribute definitions

/work-attributes (Work Attributes)

AO_013613_WA_SL_VALUE

Static-list values for an attribute

/work-attributes (values nested in attribute payload)

AO_013613_WA_VALUE

Attribute values attached to a worklog

/worklogs/{id}/work-attribute-values

AO_013613_EXP_CATEGORY

Expense categories

No public REST endpoint

AO_013613_EXPENSE

Expenses on issues

No public REST endpoint

AO_013613_SAVED_REPORT_V2

Saved reports

No public REST endpoint

AO_013613_FAVORITES

Favorited issues in Tempo panels

No public REST endpoint

AO_013613_PROJECT_CONFIG

Tempo project color

No public REST endpoint

Internal Issue (AO_BEE373_*)

DC table

Stores

API endpoint group

AO_BEE373_INTERNAL_ISSUE

Internal (non-Jira) issues

No dedicated REST endpoint — internal issues surface in /worklogs responses but are managed via the Tempo UI

Tempo Timesheets (AO_86ED1B_*)

Worklogs themselves live in Jira's worklog table (not an AO_ table) and are exposed via /worklogs and /worklogs/search.

DC table

Stores

API endpoint group

AO_86ED1B_PERIOD

Timesheet periods

/periods (Periods)

AO_86ED1B_PERIOD_CONFIG

Period configuration rules

No public REST endpoint

AO_86ED1B_TIMESHEET_APPROVAL

Approval action log

/timesheet-approvals/user/{accountId}, /timesheet-approvals/team/{teamId} (Timesheet Approvals)

AO_86ED1B_GRACE_PERIOD_V2

Granted grace periods

No public REST endpoint

AO_86ED1B_WORKLOG_EXT_PROP

Servlet API external log

Tempo Servlet API, not the REST API

Tempo Accounts (AO_C3C6E8_*)

DC table

Stores

API endpoint group

AO_C3C6E8_ACCOUNT_V1

Tempo accounts

/accounts (Accounts), /accounts/search

AO_C3C6E8_CATEGORY_V1

Account category types

/account-categories (Account Categories)

AO_C3C6E8_CUSTOMER_V1

Customers

/customers (Customers)

AO_C3C6E8_LINK_V1

Account-to-project links

/account-links (Account Links)

AO_C3C6E8_RATE

Price tables for roles

No public REST endpoint (rate tables are admin-UI only)

AO_C3C6E8_RATE_TABLE

Account-to-rate-table mapping

No public REST endpoint

Tempo Teams (AO_AEFED0_*)

DC table

Stores

API endpoint group

AO_AEFED0_TEAM_V2

Tempo teams

/teams (Teams)

AO_AEFED0_TEAM_MEMBER_V2

Team member entries (user/group)

/teams/{teamId}/members

AO_AEFED0_MEMBERSHIP

Membership instances (role + dates)

/team-memberships (Team Memberships)

AO_AEFED0_TEAM_ROLE

Team roles

/roles (Roles)

AO_AEFED0_TEAM_LINK

Team-to-project links

/team-links (Team Links)

AO_AEFED0_PROGRAM

Tempo programs

/programs (Programs)

AO_AEFED0_GENERIC_RESOURCE

Generic resources

/generic-resources (DC) / nested under teams in Cloud

AO_AEFED0_GR_TEAM_MEMBER

Generic resource ↔ team

/team-memberships (with generic-resource type)

AO_AEFED0_USER_INDEX

Tempo's user index

No Tempo endpoint — use Jira's /rest/api/2/user

AO_AEFED0_LOCATION

Locations

No public REST endpoint

AO_AEFED0_TEAM_PERMISSION

Per-member team permissions

No public REST endpoint

AO_AEFED0_PGP_GROUP_V2

Team permission groups

No public REST endpoint

AO_AEFED0_PGP_PERMISSION_V2

Permissions in a group

No public REST endpoint

AO_AEFED0_PGP_GROUP_TO_TEAM

Permission group ↔ team

No public REST endpoint

Tempo Planner (AO_2D3BEA_PLAN_*)

DC table

Stores

API endpoint group

AO_2D3BEA_PLAN_ALLOCATION

Tempo plans

/plans, /plans/search (Plans)

AO_2D3BEA_PLAN_APPROVAL_LOG

Plan approval log

No public REST endpoint on DC

Tempo Budgets — Folios/Portfolios (AO_2D3BEA_*, non-plan)

The entire Budgets/Folio data set (PORTFOLIO, FOLIOTOPORTFOLIO, BASELINE, POSITION, ALLOCATION, RATE, CURRENCY, EXCHANGERATE, STATUS, WEEKDAY, WAGE, OVERTIME, FOLIO_MATRIX, EXTERNALTEAM, FOLIOCF, FOLIOCFVALUE, EXPENSE, ATTACHMENT, COMMENT, PORTFOLIO_ADMIN, PORTFOLIOTOPORTFOLIO) is not exposed via the public REST API documented at apidocs.tempo.io. Tempo Budgets has historically only had a limited Java/Servlet API; for reporting, the KB article specifically directs you to query these tables directly or use the Servlet API.

A few practical notes worth highlighting:

  • For worklog data, don't query AO_* tables — Tempo writes to Jira's standard worklog table and uses AO_013613_WA_VALUE only for the work-attribute values. Use POST /worklogs/search to get both together in one call.

  • For timesheet approval status, the KB explicitly recommends the Servlet API over reading AO_86ED1B_TIMESHEET_APPROVAL directly; the equivalent REST endpoints are under /timesheet-approvals.

  • The DC REST API documentation lives at apidocs.tempo.io/dc/ (split into tempo-core, tempo-timesheets, tempo-teams, tempo-accounts, tempo-planning modules) — worth bookmarking alongside the Cloud docs you linked, since the resource paths differ slightly even though the groupings line up.

The above information is mainly to understand how Tempo data are related between Data Center and Cloud platforms. It’s not meant for manual data migration. It’s always recommended to use JCMA for Data Center to Cloud Migration. Please refer to Tempo Migration Guide for more info.