FAQ

Change callsign (Promotion, Class change, etc)

We can change your callsign keeping your contacts and settings from the previous callsign. To do this, send a request to support@hampass.org with your new license attached - REQUIRED: Only requests with new license will be analyzed.

Account verification

If you did not submit your license when registering, or your license has expired and you obtained a new one, you can request re-verification by sending your new license to support@hampass.org - Explain the situation on e-mail body.

Managing organizations

You can add your organizations (radio clubs, repeaters, scout groups or others) in guide of this site. To do this, click on "GUIDE", select your country and click on "Add new organization" in the upper right corner.

Membership

You can join existing groups online. To do this, click on "Membership" on the group's profile page.

To leave group, click on "leave" button.

Your admission needs to be approved by an admin member of the group.

Updating profile

Over time, you may need to update your group information. You can do this if you are an admin user of the group. To do so, simply click the "Update profile" button on the group's profile page.

Sending logs

Both formats (Adif and Cabrillo 3.0) are accepted in HamPass.

You can send your logs without fear, our system prevent any capability of duplication.

Files smaller than 200kb are processed immediately, larger files are sent to the processing queue.

Realtime

To use realtime sending on your DX or DX Expedition, please, follow these instructions.

Contact confirmation

QSO records are automatically confirmed when the informations about sender and receiving (two logs) are matching in frequency, mode, callsign and time. The accepted difference in datetime is 5 minutes for contests and 30 minutes for general logs.

Developers

Dear developer, integrate your application on HamPass world! We have some options to get logs, send logs and more.

Logbook frame

For sites that do not accept the inclusion of javascript codes, you can use our logbook frame.

<iframe src="https://hampass.org/api/logbox.html?callsign=YOURCALLSIGN" align="top" frameborder="0" height="500" scrolling="yes" style="width:100%;height:500px;" ></iframe>

* Replace YOURCALLSIGN by desired callsign

Realtime logbook box

Insert HamPass logbook box on your site introducing a JavaScript code in your HTML code, see:

<script type="text/javascript" src="https://hampass.org/api/logbox.js?callsign=YOURCALLSIGN"></script>

* Replace YOURCALLSIGN by desired callsign

Realtime logbook API

Get your contacts (in realtime) using the realtime logbook API.

URL: https://hampass.org/api/logbook.json
POST PARAMS:


• callsign -> Callsign of user
• search -> Search callsign
• recNo -> Pagination (record number)
• lastUpdate -> Last received records update datetime (hot data)

RETURN:
Array of:

• datetime -> Datetime of contact (Y-m-d H:m:s)
• to -> Contact callsign
• frequency -> Frequency (in MHz)
• mode -> Mode (SSB, CW, FT8, RTTY, ...)
• comments -> Coments about logged contact
• _OPERATOR_NAME -> Name of operator (if is registered in HamPass)
• _COUNTRY -> Text of JSON data about country of contact (ISO AND entity name)

Login API

Identify your users/visitors using HamPass API and get profile of users.

URL: https://hampass.org/api/login.json
POST PARAMS:


• callsign -> User account callsign
• password -> Password :P

RETURN:
Object:

• error -> Numeric error code (0: sucessfull, 1: invalid e-mail or callsign, 2: incorrect password)
• hash -> Login hash code (token) - for one use only (unique in each operation)

Client API

Send logs via AJAX to HamPass logbook.

Notes about contact data update

If you want to update contact data, resend the contact with the adjusts. HamPass will consider the same contact if you are using one of this combinations:

Previous Callsign + Previous Datetime + New Frequency

Previous Callsign + New Datetime (maximum 10 minutes difference) + Previous Frequency

New Callsign + Previous Datetime + Previous Frequency

URL: https://hampass.org/api/client.json
POST PARAMS:


• auth_callsign -> User account callsign
• auth_hash -> Auth totem (get by login API)
• log -> Contacts in JSON format
  Array of:
  
  • datetime -> Datetime of contact (Y-m-d H:m:s)
  • frequency -> Frequency in MHz
  • callsign -> Contact callsign
  • mode -> Mode (SSB, CW, FT8, RTTY, ...)
  • RSTSent -> Sent RST
  • EXCSent -> Sent exchange
  • RSTRecv -> Received RST
  • EXCRecv -> Received exchange

RETURN:
Object:

• error -> Numeric error code (0: sucessfull, 1: invalid e-mail or callsign, 2: invalid authentication hash)
• auth_hash -> New authentication hash code (token) for next operation