# Logbooks need to be able to be configured as POTA activities via API | API | KB0RB

**URL:** <https://community.worldradioleague.com/t/logbooks-need-to-be-able-to-be-configured-as-pota-activities-via-api-api-kb0rb/46741>\
**Category:** Feature Requests\
**Created:** [October 12, 2026, 10:30pm UTC](https://community.worldradioleague.com/t/logbooks-need-to-be-able-to-be-configured-as-pota-activities-via-api-api-kb0rb/46741 "2026-10-12T22:30:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![N0WRL](https://sea1.discourse-cdn.com/flex019/user_avatar/community.worldradioleague.com/n0wrl/32/38628_2.png) [@N0WRL](https://community.worldradioleague.com/u/N0WRL)\
**Post date:** [October 12, 2026, 10:30pm UTC](https://community.worldradioleague.com/t/logbooks-need-to-be-able-to-be-configured-as-pota-activities-via-api-api-kb0rb/46741/1 "2026-10-12T22:30:29Z")

</div>

New feature request by @KB0RB!

Hi there! Me again. I created Greyline FT8 and integrated WRL API logging into it. When my users run a POTA activation, I create a new WRL logbook per activation and record their QSOs into it. However, those logbooks can’t be marked as a POTA activity via the API. The user has to go back later and update them manually - adding a park, setting their operator callsign (which also can’t be set via the API), and location. This is a big hassle and something that should be easily accepted at create time as parameters.