Tender API Lambda

The pn-paper-channel-tenderAPILambda Lambda function provides read-only access to pn-paper-channel data without going through the REST back-office API. You invoke it directly using the AWS SDK or CLI, passing a JSON payload that specifies an operation and its parameters.

Use this Lambda when you need programmatic or internal access to tender data from within the AWS ecosystem (e.g., from other Lambda functions, scripts, or automation pipelines). For back-office user-facing operations and write access, use the back-office REST API instead.

Function name

pn-paper-channel-tenderAPILambda

Replace X in the AWS SSO profile sso_pn-core-X with the appropriate environment identifier (e.g., dev, uat, prod).

Invocation pattern

All operations share the same invocation pattern. Set operation in the payload to select which operation to run.

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '<payload-json>' \
  response.json

The --payload value must be a JSON string. On some systems you may need to base64-encode it: --payload $(echo '<json>' | base64).

Operations

GET_TENDERS — list all tenders

Returns a paginated list of tenders. You can narrow results with an optional date range filter.

Payload

operation

string

required

Must be "GET_TENDERS".

page

number

required

Zero-based page number to retrieve (integer).

size

number

required

Number of items per page (integer).

from

string

Start of the date range filter. ISO 8601 UTC format, e.g. 2024-01-01T08:00:00.000Z.

string

End of the date range filter. ISO 8601 UTC format, e.g. 2024-12-31T23:59:59.999Z.

Response

statusCode

number

required

200 on success, 400 on input validation error.

description

string

required

Human-readable description of the result.

content

PaperChannelTender[]

Paginated list of tender objects. Empty array when no tenders match the filter.

Show PaperChannelTender properties

tenderId

string

Unique tender identifier.

name

string

Human-readable tender name.

activationDate

string

Tender activation date. ISO 8601 UTC format.

vat

number

VAT percentage (integer).

nonDeductibleVat

number

Non-deductible VAT percentage (integer).

pagePrice

number

Price per page (float).

basePriceAR

number

Base price for AR product (float).

basePriceRS

number

Base price for RS product (float).

basePrice890

number

Base price for 890 product (float).

fee

number

Fee amount (float).

active

boolean

true if the tender is currently active.

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	Tenders filtered by the provided query parameters
`400`	Input data format error

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_TENDERS","page":0,"size":10,"from":"2024-01-01T00:00:00.000Z","to":"2024-12-31T23:59:59.999Z"}' \
  response.json

GET_TENDER_ACTIVE — get the currently active tender

Returns the single tender that is currently active. Returns 404 if no active tender exists.

Payload

operation

string

required

Must be "GET_TENDER_ACTIVE".

Response

statusCode

number

required

200 on success, 400 on input error, 404 if no active tender is found.

description

string

required

Human-readable description of the result.

content

object

The currently active tender.

Show PaperChannelTender properties

tenderId

string

Unique tender identifier.

name

string

Human-readable tender name.

activationDate

string

Tender activation date. ISO 8601 UTC format.

vat

number

VAT percentage (integer).

nonDeductibleVat

number

Non-deductible VAT percentage (integer).

pagePrice

number

Price per page (float).

basePriceAR

number

Base price for AR product (float).

basePriceRS

number

Base price for RS product (float).

basePrice890

number

Base price for 890 product (float).

fee

number

Fee amount (float).

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	Currently active tender returned
`400`	Input data format error
`404`	No active tender found

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_TENDER_ACTIVE"}' \
  response.json

GET_COSTS — list costs for a tender

Returns all costs associated with a tender. You can filter by product, lot, zone, or delivery driver.

Payload

operation

string

required

Must be "GET_COSTS".

tenderId

string

required

Unique identifier of the tender whose costs you want to retrieve.

product

string

Filter by product type (e.g., AR, RS, 890).

lot

string

Filter by lot identifier.

zone

string

Filter by delivery zone.

deliveryDriverId

string

Filter by delivery driver identifier.

Response

statusCode

number

required

200 on success, 400 on input error, 404 if the tender is not found.

description

string

required

Human-readable description of the result.

content

PaperChannelTenderCosts[]

List of cost records matching the filter.

Show PaperChannelTenderCosts properties

tenderId

string

Tender identifier.

productLotZone

string

Composite key combining product, lot, and zone.

product

string

Product type (AR, RS, or 890).

lot

string

Lot identifier.

zone

string

Delivery zone.

deliveryDriverName

string

Business name of the delivery driver.

deliveryDriverId

string

Delivery driver identifier.

dematerializationCost

number

Dematerialization cost amount.

rangedCosts

PaperChannelTenderCostsRange[]

Weight-based cost brackets for this record.

Show PaperChannelTenderCostsRange properties

cost

number

Cost in euros for this weight range.

minWeight

number

Minimum weight in grams for this bracket.

maxWeight

number

Maximum weight in grams for this bracket.

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	Costs associated with the tender ID
`400`	Input data format error
`404`	Tender not found

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_COSTS","tenderId":"tender-abc-123","product":"AR"}' \
  response.json

GET_COST — get a specific cost by tender, product, and geokey

Returns a single cost record identified by tender ID, product type, and geokey.

Payload

operation

string

required

Must be "GET_COST".

tenderId

string

required

Unique identifier of the tender.

product

string

required

Product type (e.g., AR, RS, 890).

geokey

string

required

Geographic key identifying the delivery area (CAP code or international zone).

Response

statusCode

number

required

200 on success, 400 on input error, 404 if the tender or geokey is not found.

description

string

required

Human-readable description of the result.

content

object

The matching cost record.

Show PaperChannelTenderCosts properties

tenderId

string

Tender identifier.

productLotZone

string

Composite key combining product, lot, and zone.

product

string

Product type.

lot

string

Lot identifier.

zone

string

Delivery zone.

deliveryDriverName

string

Business name of the delivery driver.

deliveryDriverId

string

Delivery driver identifier.

dematerializationCost

number

Dematerialization cost amount.

rangedCosts

PaperChannelTenderCostsRange[]

Weight-based cost brackets.

Show PaperChannelTenderCostsRange properties

cost

number

Cost in euros for this weight range.

minWeight

number

Minimum weight in grams.

maxWeight

number

Maximum weight in grams.

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	Cost for the specified tender, product, and geokey
`400`	Input data format error
`404`	Tender or geokey not found

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_COST","tenderId":"tender-abc-123","product":"AR","geokey":"00100"}' \
  response.json

GET_GEOKEY — get versions of a specific geokey

Returns all historical versions of a geokey for a given tender and product combination. This is useful for auditing coverage changes over time.

Payload

operation

string

required

Must be "GET_GEOKEY".

tenderId

string

required

Unique identifier of the tender.

product

string

required

Product type (e.g., AR, RS, 890).

geokey

string

required

Geographic key to look up (CAP code or international zone identifier).

Response

statusCode

number

required

200 on success, 400 on input error.

description

string

required

Human-readable description of the result.

content

PaperChannelGeokey[]

List of geokey version records.

Show PaperChannelGeokey properties

tenderProductGeokey

string

Composite primary key: combination of tender ID, product, and geokey.

activationDate

string

Date this geokey version became active. ISO 8601 UTC format.

tenderId

string

Tender identifier.

product

string

Product type.

geokey

string

Geographic key value.

lot

string

Lot identifier associated with this geokey version.

zone

string

Zone associated with this geokey version.

coverFlag

boolean

true if this geokey is covered by the delivery driver.

dismissed

boolean

true if this geokey version has been dismissed (superseded by a newer version).

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	List of geokey versions
`400`	Input data format error

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_GEOKEY","tenderId":"tender-abc-123","product":"AR","geokey":"00100"}' \
  response.json

GET_DELIVERY_DRIVERS — list all delivery drivers

Returns a list of all delivery drivers registered in the system.

Payload

operation

string

required

Must be "GET_DELIVERY_DRIVERS".

Response

statusCode

number

required

200 on success, 400 on input error.

description

string

required

Human-readable description of the result.

content

PaperChannelDeliveryDriver[]

List of all delivery driver records.

Show PaperChannelDeliveryDriver properties

deliveryDriverId

string

Unique delivery driver identifier.

taxId

string

Company tax ID (Partita IVA).

businessName

string

Company business name.

fiscalCode

string

Italian fiscal code (codice fiscale).

pec

string

PEC (certified email) address.

phoneNumber

string

Phone number.

registeredOffice

string

Registered office address.

createdAt

string

Record creation timestamp. ISO 8601 UTC format.

Status codes

Code	Description
`200`	List of delivery drivers
`400`	Input data format error

AWS CLI example

aws lambda \
  --profile sso_pn-core-X \
  invoke \
  --function-name pn-paper-channel-tenderAPILambda \
  --payload '{"operation":"GET_DELIVERY_DRIVERS"}' \
  response.json

Lambda vs REST API

Capability	Lambda	Back-office REST API
Read tenders	Yes	Yes
Read costs and geokeys	Yes	Yes (costs only)
Read delivery drivers	Yes	Yes
Create / update / delete	No	Yes
Authentication	AWS IAM / SSO profile	`x-api-key` header
Best for	Internal automation, scripts, other Lambda functions	Back-office UI, external integrations

The Lambda function is read-only. For any write operations (creating or updating tenders, drivers, or costs), use the back-office REST API.

Internal API

Back-Office API

Lambda API

Function name

Invocation pattern

Operations

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Lambda vs REST API

Build docs developers (and LLMs) love

Internal API

Back-Office API

Lambda API

​Function name

​Invocation pattern

​Operations

​Payload

​Response

​Status codes

​AWS CLI example

​Payload

​Response

​Status codes

​AWS CLI example

​Payload

​Response

​Status codes

​AWS CLI example

​Payload

​Response

​Status codes

​AWS CLI example

​Payload

​Response

​Status codes

​AWS CLI example

​Payload

​Response

​Status codes

​AWS CLI example

​Lambda vs REST API

Build docs developers (and LLMs) love

Function name

Invocation pattern

Operations

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Payload

Response

Status codes

AWS CLI example

Lambda vs REST API