2025-32

[michielbdejong]

Working 5x2 hours on Syncables this week.

Some private errands and reminders in https://github.com/michielbdejong/private-notes/issues/7

I ran the script again, it indeed does a one-sweep full sync.
I should add authentication but for now I think it's fine, it's not the most interesting part to work on.
I should work more on idempotency and reliable updating. I think I'll continue to use the Google Calendar API as an example, and within that at first the calendars collection. Not sure if this API can be used to create a new calendar.

[michielbdejong]

curl 'https://agent.dev.eduwallet.nl/mbob/api/create-offer' \
  -X POST \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer KZrytiX6RXDaXIUnstjCKyr1SRIblhWi' \
  --data-raw '{"credentials":["OpenBadgeCredential"],"grants":{"urn:ietf:params:oauth:grant-type:pre-authorized_code":{"pre-authorized_code":"generate"}},"credentialDataSupplierInput":{"achievement":{"name":"A Wonderful Thing","description":"Doing something wonderful"},"result":{"grade":"A","comment":"This person did something wonderful"}},"credentialMetadata":{"expirationDate":"2030-01-01 01:23:45","issuanceDate":"2020-01-01 12:34:56","evidence":{"type":"EvidenceType","url":"url entry","data":"additional data"}}}'

-> {"uri":"openid-credential-offer://?credential_offer_uri=https://agent.dev.eduwallet.nl/mbob/get-credential-offer/e7d8a60b210645ae898c51a97ea31de3","id":"e7d8a60b210645ae898c51a97ea31de3"}

curl https://agent.dev.eduwallet.nl/mbob/get-credential-offer/e7d8a60b210645ae898c51a97ea31de3

-> {"grants":{"urn:ietf:params:oauth:grant-type:pre-authorized_code":{"pre-authorized_code":"469e803d25dd414391cdf4cc392181c2"}},"credential_configuration_ids":["OpenBadgeCredential"],"credential_issuer":"https://agent.dev.eduwallet.nl/mbob"}

[michielbdejong]

For the Google API key and access token, it's easy to get an API key from the console, but then to obtain the access token you need to do actual OAuth. Maybe I need to put up a simple webpage on localhost:3000 for this.

https://www.passportjs.org/concepts/authentication/oauth/

[michielbdejong]

Recommendations feature for SURF:
Fediverse as the base.
Internet Archive?
What about access control in fediverse? Recommendations are usually public.

[michielbdejong]

curl -X POST https://common-sandbox.api.acubeapi.com/login -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"email": "acube@pondersource.com", "password": "..."}' -i

[michielbdejong]

{
  "email": "acube@pondersource.com",
  "fullname": "Pondersource",
  "invoicing_vat_number": null,
  "invoicing_fiscal_id": null,
  "invoicing_address": null,
  "invoicing_city": null,
  "invoicing_province": null,
  "invoicing_cap": null,
  "invoicing_name": null,
  "invoicing_country": null,
  "invoicing_sdi_recipient_code": null,
  "invoicing_sdi_pec": null,
  "logo_url": null
}

[michielbdejong]

Sending this body in https://docs.acubeapi.com/documentation/peppol/peppol/tag/LegalEntity/#tag/LegalEntity/operation/api_legal-entities_post:

{
  "registeredName": "Ponder Source",
  "country": "SE",
  "address": "string",
  "city": "string",
  "stateOrProvince": "string",
  "zipCode": "string",
  "identifierScheme": "iso6523-actorid-upis",
  "identifierValue": "0007:5567212047",
  "receivedDocumentNotificationEmails": [
    "notif@pondersource.com"
  ]
}

I get this output:

{
  "@context": {
    "@vocab": "http://peppol-sandbox.api.acubeapi.com/docs.jsonld#",
    "hydra": "http://www.w3.org/ns/hydra/core#",
    "uuid": "LegalEntityOutput/uuid",
    "registeredName": "LegalEntityOutput/registeredName",
    "country": "LegalEntityOutput/country",
    "address": "LegalEntityOutput/address",
    "city": "LegalEntityOutput/city",
    "stateOrProvince": "LegalEntityOutput/stateOrProvince",
    "zipCode": "LegalEntityOutput/zipCode",
    "identifierScheme": "LegalEntityOutput/identifierScheme",
    "identifierValue": "LegalEntityOutput/identifierValue",
    "receivedDocumentNotificationEmails": "LegalEntityOutput/receivedDocumentNotificationEmails",
    "smpEnabled": "LegalEntityOutput/smpEnabled",
    "createdAt": "LegalEntityOutput/createdAt",
    "updatedAt": "LegalEntityOutput/updatedAt"
  },
  "@type": "LegalEntityOutput",
  "@id": "/.well-known/genid/7cd34480327af0b76253",
  "uuid": "0e5976d6-949d-4954-a09a-77a2e38ac65a",
  "registeredName": "Ponder Source",
  "country": "SE",
  "address": "string",
  "city": "string",
  "stateOrProvince": "string",
  "zipCode": "string",
  "identifierScheme": "iso6523-actorid-upis",
  "identifierValue": "0007:5567212047",
  "receivedDocumentNotificationEmails": [
    "notif@pondersource.com"
  ],
  "smpEnabled": false,
  "createdAt": "2025-08-15T05:47:26+00:00",
  "updatedAt": ""
}

[michielbdejong]

Next: https://docs.acubeapi.com/documentation/peppol/peppol/tag/Invoice/#tag/Invoice/operation/api_invoices_post_outgoing_ubl_collection

[michielbdejong]

Architecture brainstorm:

Allereerst gaan wij zelf een database bijhouden van onze gebruikers, en daar zitten dan denk ik ook nog twee lagen in: API keys voor ontwikkelaars en KYC credentials (dus BTW nummers) voor eind-gebruikers. Maar om het simpel te houden kunnen we opleggen dat er (in eerste instantie) maar 1 BTW nummer aan een API key gekoppeld kan worden.

API calls:

• aanmelden, met:
    * het Belgische BTW nummer dat je wilt claimen
    * de webhook waar je notificaties wilt ontvangen
• verstuur een UBL invoice
• op de webhook: 
  • notifications rondom verstuurde UBL invoices
  • notifications rondom ontvangen UBL invoices

We hebben wel een staging en productie environment nodig. In staging wordt de aanmeld-code direct getoond. In productie wordt die door onze echte KYC module bijvoorbeeld per brief naar je postadres gestuurd.

[michielbdejong]

TUBS milestones for NLnet

KYC-AS for Peppol 5
Auth & dispatch Proxy for Peppol 5
Demo app for Peppol 5
Syncables 1.0 5
Syncables 2.0 5
Devonian 1.0 5
Devonian 2.0 5
Reflector 5
Demo for fintech 5
Demo for PDS 5