Documentation: targets

This tables saves targets data for Ascent reports submitted by PIUs. It allows for tracking and validation of targets set for various metrics.
To import data in this format you can use our API. -> API Documentation
Rate limit: 300 requests per minute. Once the limit is exceeded, any further requests will result in a 429 (Too Many Requests) response.
You can also supply us with files in xlsx, csv or json format. -> Example CSV
Row Name Type Example

metric *

The specific metric for which the target is set.

  • * required
string

People provided with new or improved electricity service

target_value *

The target value for the specified metric.

Only period (.) decimal delimiters are supported. Do not use commas (,) — they will cause an error.

  • * required
float

100.0

unit_of_measurement *

Unit of measurement for the metric being tracked, such as kWh, number of connections, etc.

  • * required
string

number

effective_date *

The date when the target was effective.

  • * required
date

2023-01-01

country *

Two-letter country code as per ISO 3166-1 alpha-2 standard representing the country of the report.

  • * required
string

RW

reporting_phase *

Unique identifier for the reporting phase, typically a sequential alpha-numeric code. It helps us identify the ASCENT phase or project that the reported data belongs to.

  • * required
string

P001

program *

This helps us extend the use cases for this table by linking it to the program under which the report was submitted, helping to categorize the data and link it to specific programs.

  • * required
string

ASCENT

program_end_date *

The end date of the program for which the target is set.

  • * required
date

2030-12-31

uid

Unique identifier of a single target entry generated by concatenating the following fields: [organization_id, source_id and external_id].

  • auto-generated
string

123_12_c782c9d4731f26d3d040d6a4a24ebd66

external_id

External identifier generated by concatenating and hashing multiple fields: [metric, effective_date, country, reporting_phase, program]. This ensures that identical records always produce the same UID, to enable upsert and deduplication operations.

  • auto-generated
string

c782c9d4731f26d3d040d6a4a24ebd66

created_at

Timestamp when row was inserted

  • auto-generated
datetime

2021-05-03 6:23:55

updated_at

Timestamp when row was updated

  • auto-generated
datetime

2021-05-03 6:23:55

source_id

References Source of data

  • auto-generated
integer

1

import_id

References Import of data

  • auto-generated
integer

1

organization_id

References Organization of data

  • auto-generated
integer

1

custom

Saves additional imported data out of standard structure

  • auto-generated
jsonb

{ "some": "key" }

data_origin

Origin of the data, generic or name of the api

  • auto-generated
string

generic

last_import_id

Id of the last import which updated the record

  • auto-generated
integer

337

last_source_id

Id of the last Source which updated the record

  • auto-generated
integer

33